Hi there,
Since 2.x piping logs into SSHGuard via stdin gave a warning:
# sshguard
sshguard: Reading from stdin. You probably shouldn't be doing this.
This behavior is being considered for removal because it prevents
resolution of issue #90, where the driver script ignores signals sent to
it. Note that killing the process indicated in the PID file set by '-i'
continues to work, because that reports the PID of sshg-blocker.
Does anyone still depend on this behavior? If so, please let me know why
and what we can do to work around it.
--
Kevin Zheng
kev...@gm... | ke...@be... | PGP: 0xC22E1090
|
