Bug#381814: changed exit status of log_end_msg breaks a bunch of packages

2006-08-09 Thread Peter Eisentraut
Stephen Gran wrote: > I would argue that this is a bug in itself. If s-s-d exits non-zero, > then the script (being set -e, right? Policy and all) will exit > right there and you'll never get to log_end_msg. Note that LSB forbids set -e to be active while LSB init functions are called. So thes

Bug#381814: changed exit status of log_end_msg breaks a bunch of packages

2006-08-09 Thread Stephen Gran
This one time, at band camp, Peter Eisentraut said: > A lot of packages currently code their init scripts like this: > > log_daemon_msg "Starting foo" > start-stop-daemon foo > log_end_msg $? I would argue that this is a bug in itself. If s-s-d exits non-zero, then the script (being set -e, righ

Bug#381814: changed exit status of log_end_msg breaks a bunch of packages

2006-08-06 Thread Peter Eisentraut
Package: lsb-base Version: 3.1-11 Severity: serious A lot of packages currently code their init scripts like this: log_daemon_msg "Starting foo" start-stop-daemon foo log_end_msg $? Since log_end_msg now returns 0 always, numerous init scripts no longer return meaningful exit codes. I think thi