| 1 |
On Thu, 6 Oct 2005, Erik Anderson wrote: |
| 2 |
|
| 3 |
> Let me know if you have any issues getting it set up. You basically |
| 4 |
> extract the tarball to a location of your choice - |
| 5 |
> /usr/local/denyhosts in my case, copy the denyhosts.cfg to /etc, |
| 6 |
> configure it as you want, and then add the following cron job: |
| 7 |
> |
| 8 |
> * * * * * python /usr/local/DenyHosts/denyhosts.py -c /etc/denyhosts.cfg |
| 9 |
> |
| 10 |
> That will (obviously) run the script every minute. Sure, that may be |
| 11 |
> overkill, but it shouldn't hurt anything. If you keep your old |
| 12 |
> logfiles, you can manually run them through denyhosts. The script is |
| 13 |
> able to deal gracefully with gzipped logfiles. Look through the |
| 14 |
> documentation to see how to do this. |
| 15 |
|
| 16 |
Forget tarballs - there's an ebuild in Gentoo's Bugzilla: |
| 17 |
http://bugs.gentoo.org/show_bug.cgi?id=100043 |
| 18 |
|
| 19 |
You need the ebuild, the init script and the patch. Create a local portage |
| 20 |
overlay and away you go. |
| 21 |
|
| 22 |
I have it running as a daemon on a test machine right now - doesn't seem |
| 23 |
to affect the load either. |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-server@g.o mailing list |
Archives