From: Bradley G. <pi...@ma...> - 2015-01-23 20:55:30
|
On Jan 22, 2015, at 6:09 PM, LuKreme <kr...@kr...> wrote: > But maybe 10.10.2 etas broke something? > > All I see /var/log/system for sshguard are lines like: > > /var/log/system.log:Jan 22 00:02:03 Jaka.local sshguard[158]: Source '/var/log/system.log' reappeared. Reloading. > /var/log/system.log.0.gz:Jan 21 15:08:08 Jaka.local sshguard[175]: Source '/var/log/system.log' reappeared. Reloading. > /var/log/system.log.0.gz:Jan 21 15:16:44 Jaka.local sshguard[158]: Started successfully [(a,p,s)=(40, 420, 1200)], now ready to scan. > /var/log/system.log.1.gz:Jan 21 00:00:15 Jaka-2.local sshguard[162]: Source '/var/log/system.log' reappeared. Reloading. > > $ psa sshg > root 158 0.0 0.0 2473568 1604 ?? S Wed03PM 0:02.23 /opt/local/sbin/sshguard -l /var/log/system.log -w /opt/local/etc/sshguard/whitelist > root 151 0.0 0.0 2463068 1008 ?? S Wed03PM 0:00.00 /bin/sh /opt/local/libexec/sshguard/sshguard-options-wrapper > root 60 0.0 0.0 2469232 1080 ?? Ss Wed03PM 0:00.01 /opt/local/bin/daemondo --label=sshguard --start-cmd /opt/local/libexec/sshguard/sshguard-options-wrapper ; --pid=exec What happens when you use SSHGUARD_DEBUG: http://www.sshguard.net/docs/faqs/#debugging Regards, Bradley Giesbrecht (pixilla) |