|
From: jonetsu <jo...@te...> - 2015-08-14 14:06:04
|
> From: "Kevin Zheng" <kev...@gm...> > Date: 08/13/15 23:18 Hello, > What operating system are you running? What version of > SSHGuard? The fix for the iptables lock landed shortly before > 1.6.0. This is a Debian platform. The version is 1.5. >> My question is: does sshguard execute any iptables command when >> terminating ? > Yes, it runs iptables to flush blocked addresses. I got the tarball generated by the web site and looked at the Changes file under 1.6 section, and did not see anything pertaining to this lock problem. The code does not mention 'xlock' specifically. If I consider sshguard as a black box, then what I thought of doing is to add a --wait (-w) switch to my iptables call, which will make iptables wait until the xlock is removed. That amount of time looks like rather short, since the xlock condition does not happen every time. Looks like it's dependent on the CPU being jusy a bit too busy at that time, from some other process. I'm curious about how a lock problem appeared *within* sshguard... Can you explain what the problem was ? Thanks ! |