Package: heimdal-kdc
Version: 1.3.1.rc2.dfsg.1-3
Severity: normal

The current heimdal-kdc init script uses set -e, which is generally
considered a bad idea.  See, for instance, /etc/init.d/skeleton:

# Do NOT "set -e"

The problem with set -e for init scripts is that Debian Policy requires
that things that will result in non-zero exit statuses be regarded as
success, such as starting something that's already running or stopping
something that's already stopped.  While you can carefully check all
exit statuses in a way that's safe for set -e, it's annoying and tricky
to do and it's usually easier to just not use it.

I discovered this problem when I was upgrading the heimdal-kdc package
and the new package could not install because I'd stopped the KDC already
and /etc/init.d/heimdal-kdc stop was failing (due to set -e) because it
couldn't stop the servers.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to