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 these scripts are not set -e, and there is no policy about that either, anyway. > > Since log_end_msg now returns 0 always, numerous init scripts no > > longer return meaningful exit codes. > > I think they were already broken. log_end_msg is what it is, and it's used the way it's used. If you want something that behaves differently, you need to invent a new function name or organize a transition. You can't just change the API on a whim and declare all previous uses of the API incorrect on the spot. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
