|
From: Kevin Z. <kev...@gm...> - 2016-05-09 20:25:53
|
Hi Jef, On 05/09/2016 12:19, Jef Poskanzer wrote: > After a reminder that portsnap exists, I updated everything and > tried again with sshguard 1.6.4. I undid my syslog config quick-fix > to test, and can confirm that the restart looping still happens > although with different log messages: > > May 9 11:57:02 hydra sshguard[22878]: Monitoring attacks from stdin > May 9 12:00:00 hydra sshguard[22878]: Received EOF from stdin > May 9 12:00:00 hydra sshguard[22878]: Exiting on signal > May 9 12:00:00 hydra sshguard[28419]: Monitoring attacks from stdin > > Looks like the exit message is now logged at level info instead > of notice, but that is still high enough to get caught by the > recommended syslog.conf line. And anyway the new 'Received EOF' > message is at level notice. Thanks for updating to 1.6.4. Could you try starting SSHGuard as a daemon using the rc.d script and see if the problem persists? Thanks, Kevin -- Kevin Zheng kev...@gm... | ke...@be... | PGP: 0xC22E1090 |