However the script itself now seems not to be runned, according to system.log: Dec 9 01:23:20 mac02 com.apple.launchd[1] (org.sourceforge.denyhosts): Throttling respawn: Will start in 8 seconds Dec 9 01:23:29 mac02 com.apple.launchd[1] (org.sourceforge.denyhosts): Throttling respawn: Will start in 9 seconds Dec 9 01:27:21 mac02 com.apple.launchd[1] (org.sourceforge.denyhosts): Throttling respawn: Will start in 4 seconds Dec 9 01:31:52 mac02 com.apple.launchd[1] (org.sourceforge.denyhosts): Throttling respawn: Will start in 8 seconds
And denyhosts.log doesn't seem to be update, or is that the correct behaviour if denyhosts is not running in daemon mode?
In our situation denyhosts is being executed as:python /usr/local/bin/denyhosts.py -c /usr/share/denyhosts/ denyhosts.cfg -n --purge --sync
When issueing this from the command-line, the result is as follows: DenyHosts could not obtain lock (pid: 4103) [Errno 17] File exists: '/var/run/denyhosts.pid'This file has already been removed manually, but within a few minutes, this error reappears.
How to solve this problem permanently? Best, Ceriel PS Running on Mac OS X 10.5.5, Python 2.5.1
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
