Your message dated Wed, 15 Nov 2006 08:42:58 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398740: init.d script does not appear idempotent
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fail2ban
Version: 0.7.4-3
Severity: normal
Could the init.d script please fail if it's asked to stop
a non-running daemon, or asked to start an already-running one?
lapse:~# /etc/init.d/fail2ban start || echo failure
Starting authentication failure monitor: fail2ban.
lapse:~# /etc/init.d/fail2ban start || echo failure
Starting authentication failure monitor: fail2ban.
lapse:~# /etc/init.d/fail2ban stop || echo failure
Stopping authentication failure monitor: fail2ban.
lapse:~# /etc/init.d/fail2ban stop || echo failure
Stopping authentication failure monitor: fail2ban.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages fail2ban depends on:
ii iptables 1.3.6.0debian1-3 administration tools for packet fi
ii lsb-base 3.1-19 Linux Standard Base 3.1 init scrip
ii python 2.4.4-1 An interactive high-level object-o
ii python-central 0.5.10 register and build utility for Pyt
ii python2.4 2.4.4-1 An interactive high-level object-o
fail2ban recommends no packages.
-- no debconf information
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
--- Begin Message ---
I.
Please see debian policy
9.3.2 Writing the scripts
The init.d scripts must ensure that they will behave sensibly if invoked with
start when the service is already running, or with stop when it isn't, and that
they don't kill unfortunately-named user processes. The best way to achieve
this is usually to use start-stop-daemon.
9.4 Console messages from init.d scripts
it would describe format of lines... also we are trying to be lsb
compliant don't we?
Also here is an example:
> /etc/init.d/apache-ssl start || echo failure
Starting apache-ssl 1.3 web server....
> /etc/init.d/apache-ssl start || echo failure
Starting apache-ssl 1.3 web server....
*> /etc/init.d/apache-ssl stop || echo failure
Stopping apache-ssl 1.3 web server....
> /etc/init.d/apache-ssl stop || echo failure
Stopping apache-ssl 1.3 web server....
II.
see /etc/init.d/skeleton
even if the daemon is running (return 1 from do_start) return of init
script is 0.
If I am wrong and there is policy statement that init script must fail
if process is running already - please cite it and I will reopen
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
pgpcCtaBTE9AJ.pgp
Description: PGP signature
--- End Message ---
