Debhelper-generated postinst and prerm vs. manual one
Henrique de Moraes Holschuh
hmh at debian.org
Fri Oct 20 19:22:27 UTC 2006
On Fri, 20 Oct 2006, Fabian Fagerholm wrote:
> 1. saslauthd binary missing from /usr/sbin
>
> If the saslauthd binary hasn't been placed in /usr/sbin when dpkg runs
Package was removed but not purged. Really, this is a standard issue with
all cron jobs and init scripts.
> -# Exit if the package is not installed
> -[ -x "$DAEMON" ] || exit $EXIT_ERROR_CODE
> -
Do not remove this. It would be a big bug.
> -# If the daemon is not enabled, give the user a useful error and then exit
> +# If the daemon is not enabled, give the user a warning and then exit
> if [ "$START" != "yes" ]; then
> - log_failure_msg "To enable $NAME, edit /etc/default/$NAME and add START=yes"
> - exit $EXIT_ERROR_CODE
> + log_warning_msg "To enable $NAME, edit /etc/default/$NAME and set START=yes"
> + exit 0
> fi
Correct, if it is disabled, exit 0 always.
> -# If no mechanisms are defined, log this and exit
> +# If no mechanisms are defined, fall back to pam
This goes against both KISS and the principle of least surprise. If no
mechs are defined, bombing out with an error is best IMHO. Just make sure
the default for the package is to have START disabled so that saslauth is
not started by default in unconfigured state.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
More information about the Pkg-cyrus-sasl2-debian-devel
mailing list