Re: [SSHGuard-users] Blacklist and command line issue

[Kevin Z. <kev...@gm...>]

On 12/11/2017 08:29, Jos Chrispijn wrote:
> Sometimes it occors that my blacklist.db contains double entries. Mostly
> that is caused by me, using the sshguard command stupidly redundant.
> In order to prevent such, would it be possible to scan running processes
> on sshguard whenever this sshguard command is given, so that only one
> process will be allowed? Dunno if that might affect VM use of sshguard.

I'll keep that in mind but I can't promise to work on it anytime soon.

The usual answer is for a daemon to always use a PID file, and not start
if the PID file is locked by another process.

A related change would be for SSHGuard to store a state file, keeping
track of currently blocked addresses, so that it remembers them when
after restarting. If the state file is similarly locked, SSHGuard would
know another instance of it has started.

> What I also noticed is that if I give a sshguard command from the
> command line, it takes ages before I get my prompt back with necessary
> command output. On which I give Ctrl-C which then may cause the first
> issue I described above.

Are you saying that when you start SSHGuard from the command line, no
output appears?

-- 
Kevin Zheng
kev...@gm... | ke...@be... | PGP: 0xC22E1090