Jason Lingohr wrote: > On 30/08/2008 11:49 AM, René Berber wrote: >> Jason Lingohr wrote: >> >> [snip] >>> No other ideas? >> Just clean it manually, it works. >> >> Don't forget to stop denyhosts first, then grep >> /usr/share/denyhosts/data en delete all ocurrences of the IP, delete it >> from /etc/hosts.deny, and finally start denyhosts (probably in debug >> mode to see the log and make sure the IP wasn't found somewhere you missed). > > That's the thing... I've already done all this, as per my original > e-mail, and it still keeps getting re-added!
I know, I've read the messages, but something must be missing. Many of us have used the manual procedure to clean, and it works. > This is the source of my confusion; it makes no sense... Since it can't get re-added by the sync server because you don't have it enabled, then it must be added by the data in the 'data' directory or by a re-scan of the log (which shouldn't happen if the status file is left alone and the log also is left intact). The debug log should show at least when it was re-added. Worst case scenario, you'll need to add a few printf() to see what's going on, or use pydb to see the detail on denyhosts start-up. -- René Berber ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
