That particular output indicates the your changed regex is being recognized by DH. Whether or not it's working properly, that's another matter.
If you restart in --debug mode, you can tail -f the denyhosts.log and then append similar lines (as those that seem problematic) to your secure.log, save it, and see what DH is reporting in it's log.
Regards, Phil On Tue, 6 May 2008, René Berber wrote:
Phil Schwartz wrote:When you restart DH what does it show in the denyhosts.log as your FAILED_ENTRY_REGEX7? eg: tail -100l /var/log/denyhosts | grep FAILED_ENTRY_REGEX72008-05-06 16:32:28,666 - prefs : INFO FAILED_ENTRY_REGEX7: [User (?P<user>\S+) from (?P<host>\S+) not allowed because not listed in .*] Looks fine, and I recall running DH in debug mode when I made that change, if I'm not mistaken the regex was working fine judging from the debug output.
-- Regards, Phil Schwartz - http://www.phil-schwartz.com Open Source Projects: - DenyHosts: http://www.denyhosts.net - Kodos: http://kodos.sourceforge.net - ReleaseForge: http://releaseforge.sourceforge.net - Scratchy: http://scratchy.sourceforge.net - FAQtor: http://faqtor.sourceforge.net
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ Denyhosts-user mailing list Denyhosts-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/denyhosts-user
