131034 2006-04-23 15:20 0000 denyhosts 2.4 has a bug 2006-04-27 15:37:22 0000 1 1 1 Unclassified Gentoo Linux Applications 2006.0 All Linux RESOLVED FIXED http://www.mail-archive.com/denyhosts-user@lists.sourceforge.net/msg00011.html P2 normal --- 1 stephane@gorfou.ca strerror@gentoo.org stephane@gorfou.ca 2006-04-23 15:20:08 0000 The link in the URL contains what I experimented and how I solved it (2.4b) jakub@gentoo.org 2006-04-23 15:21:37 0000 Don't refer to external links for bug description. If makes searching for duplicates completely useless. stephane@gorfou.ca 2006-04-23 15:35:18 0000 If this is fixed quickly, there should not be any dupplicates. The problem has been fixed upstream with version 2.b. ------------------- # /etc/init.d/denyhosts start * Caching service dependencies ... [ ok ] * Starting DenyHosts daemon ... Traceback (most recent call last): File "/usr/bin/denyhosts", line 164, in ? first_time, noemail, daemon) File "/usr/lib/python2.4/site-packages/DenyHosts/deny_hosts.py", line 82, in __init__ offset = self.process_log(logfile, last_offset) File "/usr/lib/python2.4/site-packages/DenyHosts/deny_hosts.py", line 423, in process_log login_attempt.add(user, host, success, invalid) File "/usr/lib/python2.4/site-packages/DenyHosts/loginattempt.py", line 106, in add elif user in __restricted: NameError: global name '_LoginAttempt__restricted' is not defined DenyHosts exited abnormally ------------------- The quick fix is to edit the ebuild and add a "b" to the my_P variable like this: my_P="${my_PN}-${PV}b" digest and re-emerge. Now stop bugging me with bureaucraties. strerror@gentoo.org 2006-04-27 15:37:22 0000 in cvs, thanks for reporting