From: John H. <joh...@gm...> - 2018-01-04 05:27:25
|
Hello, When I start sshguard, like this: > sudo ./sshguard -l /var/log/auth.log it seems that three separate sshguard processes are spawned: > ps -A | grep sshg 1486 pts/1 00:00:00 sshguard 1487 pts/1 00:00:00 sshguard 1488 pts/1 00:00:00 sshg-parser 1489 pts/1 00:00:00 sshg-blocker 1491 pts/1 00:00:00 sshguard 1492 pts/1 00:00:00 sshg-fw-hosts Is this normal? Everything seems to be working, but I'm perplexed as to how three instances are started. (Unless this is intentional, in which case there's nothing to see here...) The following may or may not not be related, but I also had to change the first non-comment line of the sbin/sshguard script from: trap "trap - SIGTERM && kill 0" SIGINT SIGTERM EXIT to: trap "trap - TERM && kill 0" INT TERM EXIT to avoid the following error on starting or interrupting the script: trap: SIGTERM: bad trap (I'm not sure why my shell complains about this... see for example https://unix.stackexchange.com/questions/314554/why-do-i-get-an-error-message-when-trying-to-trap-a-sigint-signal ) Many thanks, John H |