Bug#639197: timeout program does not return exit status of executed program

2011-08-24 Thread Scott Gifford
Package: timeout Version: 1.11-6.5 Severity: normal Tags: patch The timeout program does not return the exit status of the program it runs, although it is documented to do so. The problem is that wait(2) returns a 16-bit integer, with the exit status in the high bits and the signal informatio

Bug#542515: sysvinit: bootlogd does not flush output buffer

2009-08-19 Thread Scott Gifford
Package: sysvinit Version: 2.86.ds1-61 Severity: important Tags: patch Debian-specific patches to bootlogd introduce a bug where it does not flush the standard output buffer at all unless the "-d" flag is passed. This often causes single-line messages to be missing from the boot log for a lon

Bug#540727: [Pkg-sysvinit-devel] Bug#540727: bootlogd: cannot find console device 136:0 in /dev failed!

2009-08-19 Thread Scott Gifford
If you run: /etc/init.d/bootlogd /dev/console 2>&1 it works OK. Running bootlogd after the system has booted will capture future output to the console, which may be useful, and the expected behavior of scripts in /etc/init.d is that their services can be stopped and started at will from a co

Bug#512547: module-init-tools: named pipe in /etc/modprobe.d prevents system boot

2009-01-21 Thread Scott Gifford
Package: module-init-tools Version: 3.3-pre4-2 Severity: normal Our system suffered some filesystem corruption recently, and ended up with some named pipes in the /etc/modprobe.d directory. This completely prevented our system from booting. Modprobe tried to read all files in that directory whene