Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-19 Thread Dmitry Bogatov
[2018-11-16 14:10] Cristian Ionescu-Idbohrn > [...] > > I agree, after reading the code again. The exit status is saved in > the ES variable and shown if $VERBOSE != no. Still, as the last > command in the script is ':', the script returns exit status success, > which might be a lie. We are

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-16 Thread Cristian Ionescu-Idbohrn
On Fri, 16 Nov 2018, Dmitry Bogatov wrote: > [2018-11-15 12:43] Cristian Ionescu-Idbohrn > > > The point I was trying to make is that with code like this: > > > > cd /var/log && { > > ... do stuff ... > > } > > ^ > > after the closed curly bracket above, if $? is _not_ 0

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-16 Thread Dmitry Bogatov
[2018-11-15 12:43] Cristian Ionescu-Idbohrn > The point I was trying to make is that with code like this: > > cd /var/log && { > ... do stuff ... > } > ^ > after the closed curly bracket above, if $? is _not_ 0 either the `cd' > command failed or some stuff

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2018-11-15 Thread Cristian Ionescu-Idbohrn
On Thu, 15 Nov 2018, Dmitry Bogatov wrote: > > I am aware, that this bug is 9 years old. I partially applied this > patch. See `b6022b1' at https://salsa.debian.org/debian/sysvinit. Still, things happen ;) > > Similar with above. Inverting logic will keep you on the right path. > > > > -

Bug#538334: initscripts: /etc/init.d/bootlogd oddities

2009-07-24 Thread Cristian Ionescu-Idbohrn
Package: initscripts Version: 2.86.ds1-66 Severity: normal Let me question some stuff: --- /etc/init.d/bootlogd.dpkg-dist 2009-07-15 00:40:37.0 +0200 +++ /etc/init.d/bootlogd2009-06-30 18:52:53.0 +0200 @@ -12,12 +11,12 @@ ### END INIT INFO PATH=/sbin:/bin # No