I experienced a similar problem when I set up a new configuration the other day. Try this:
sudo touch /var/lib/denyhosts/sync-timestamp It should then sync. Let us know how it goes, Robert Jason L Tibbitts III wrote: > Is it expected behavior that the first call to denyhosts --sync will > fail? > >> sudo denyhosts.py -d -c /etc/denyhosts.conf --sync > [...] > receive_new_hosts() > [Errno 2] No such file or directory: '/var/lib/denyhosts/sync-timestamp' > received 50 new hosts > Error synchronizing data > name 'info' is not defined > > Successive attempts don't fail, but nothing is added to hosts.deny. I > don't use sync myself so I'm not sure if that's expected behavior or > not, or if I've somehow screwed up the denyhosts packaging badly > enough to break this. > > I've received a couple of reports that the denyhosts daemon will > simply hang when sync is enabled and I'm wondering if I need to ship a > default sync-timestamp file. (An empty one causes a different > failure.) > > - J< ------------------------------------------------------------------------- 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
