Bug#317786: nstx: init script doesn't report daemon start failure
On Mon, Jul 11, 2005 at 06:34:54AM -0700, Matt Taggart wrote:
> Package: nstx
> The init script for nstxcd (and maybe nstxd?) fail to report if a start
> action is unsuccessful. The one repeatable case I've discovered to
> test this is that if there is no network interface up (or default
> route) then it fails to start.
But they still reach the 'echo "$NAME."' line? This behaviour is very common
in shell scripts that use 'set -e'. If something fails they will abort
automaticaly, but you will notice because they don't reach the line where
name is printed.
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)