From: Smylers
Date: 18:36 on 24 Jul 2007
Subject: DenyHosts Locking
# denyhosts.py --daemon
DenyHosts could not obtain lock (pid: 6864)
[Errno 17] File exists: '/var/run/denyhosts.pid'
So let's try:
# denyhosts.py --daemon --unlock
Invalid command line option detected.
Usage: /usr/bin/denyhosts.py [-f logfile | --file=logfile]
[ -c configfile | --config=configfile] [-i | --ignore]
[-n | --noemail] [--purge] [--migrate] [--daemon] [--sync] [--version]
--file: The name of log file to parse
--ignore: Ignore last processed offset (start processing from
beginning)
--noemail: Do not send an email report
--unlock: if lockfile exists, remove it and run as normal
--migrate: migrate your HOSTS_DENY file so that it is suitable for
--purge
--purge: expire entries older than your PURGE_DENY setting
--daemon: run DenyHosts in daemon mode
--sync: run DenyHosts synchronization mode
--version: Prints the version of DenyHosts and exits
Nice touch; when telling me that an option is invalid it's always nice
to see the full usage information displayed, _complete with
documentation of the option that you're telling me doesn't exist_!
Smylers
From: Scott Francis
Date: 16:52 on 26 Jul 2007
Subject: Re: DenyHosts Locking
--CPn8Wy5ME997YUMW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jul 24, 2007 at 06:36:03PM +0100, Smylers@xxxxxxx.xxx said:
> # denyhosts.py --daemon
> DenyHosts could not obtain lock (pid: 6864)
> [Errno 17] File exists: '/var/run/denyhosts.pid'
>=20
> So let's try:
>=20
> # denyhosts.py --daemon --unlock
> Invalid command line option detected.
> Usage: /usr/bin/denyhosts.py [-f logfile | --file=3Dlogfile]
> [ -c configfile | --config=3Dconfigfile] [-i | --ignore]
> [-n | --noemail] [--purge] [--migrate] [--daemon] [--sync] [--version]
>=20
> --file: The name of log file to parse
> --ignore: Ignore last processed offset (start processing from
> beginning)
> --noemail: Do not send an email report
> --unlock: if lockfile exists, remove it and run as normal
> --migrate: migrate your HOSTS_DENY file so that it is suitable for
> --purge
> --purge: expire entries older than your PURGE_DENY setting
> --daemon: run DenyHosts in daemon mode
> --sync: run DenyHosts synchronization mode
> --version: Prints the version of DenyHosts and exits
>=20
> Nice touch; when telling me that an option is invalid it's always nice
> to see the full usage information displayed, _complete with
> documentation of the option that you're telling me doesn't exist_!
bonus hate: --unlock mentioned in verbose usage, and not mentioned in
brief usage.
--=20
Scott Francis | darkuncle(at)darkuncle(dot)net | 0x5537F527
Less and less is done
until non-action is achieved
when nothing is done, nothing is left undone.
-- the Tao of Sysadmin
--CPn8Wy5ME997YUMW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (OpenBSD)
iD8DBQFGqMNFWaB7jFU39ScRArmwAJ9nUwxCJi0FvNvW/P+KDSYlteDt3gCg2m5J
UfPcisyxpwwwhdCR4xVtcb4=
=ipGq
-----END PGP SIGNATURE-----
--CPn8Wy5ME997YUMW--
From: A. Pagaltzis Date: 17:07 on 26 Jul 2007 Subject: Re: DenyHosts Locking * Scott Francis <darkuncle@xxxxxxxxx.xxx> [2007-07-26 18:00]: > On Tue, Jul 24, 2007 at 06:36:03PM +0100, Smylers@xxxxxxx.xxx said: > > Nice touch; when telling me that an option is invalid it's > > always nice to see the full usage information displayed, > > _complete with documentation of the option that you're > > telling me doesn't exist_! > > bonus hate: --unlock mentioned in verbose usage, and not > mentioned in brief usage. Seems like slippage; either slipped through the feature removal or slipped out from an unreleased feature. Silly either way. Regards,
From: Edmund von der Burg Date: 18:14 on 26 Jul 2007 Subject: Re: DenyHosts Locking Or worse yet unlock will only work if it is the only option - the author thinking that you'd want to do something like this: # denyhosts.py --unlock # denyhosts.py --daemon of course this sort of usage is so blindingly obvious that there is no need to mention it in the docs or produce a helpful error message. On 26/07/07, A. Pagaltzis <pagaltzis@xxx.xx> wrote: > * Scott Francis <darkuncle@xxxxxxxxx.xxx> [2007-07-26 18:00]: > > On Tue, Jul 24, 2007 at 06:36:03PM +0100, Smylers@xxxxxxx.xxx said: > > > Nice touch; when telling me that an option is invalid it's > > > always nice to see the full usage information displayed, > > > _complete with documentation of the option that you're > > > telling me doesn't exist_! > > > > bonus hate: --unlock mentioned in verbose usage, and not > > mentioned in brief usage. > > Seems like slippage; either slipped through the feature removal > or slipped out from an unreleased feature. Silly either way. > > Regards, > -- > Aristotle Pagaltzis // <http://plasmasturm.org/>; > >
Generated at 10:27 on 16 Apr 2008 by mariachi