Bug#534562: nfdump: please reconsider VERBOSE handling in init script

2009-07-01 Thread Erik Wenzel

Hi Marc,

Am 25.06.2009 um 12:15 schrieb Marc Haber:


Package: nfdump
Version: 1.5.7+20081221-3
Severity: wishlist

Hi,

I usually boot my kernel with a "quiet" command line since I don't
want the system to spew screenfuls of init messages before the splash
screen takes over. This, as a - surprising - side effect causes
/lib/init/vars.sh to set the VERBOSE environment variable which in
turn causes nfdump's init script to totally silence itself. This comes
as a surprise.

IMO, the wish to have a noiseless system start does not include the
wish that an init script which may be invoked from the command line
days later does not give any feedback about its operation.

Please consider returning your init script to the behavior that is
common for init scripts, which is not honoring a VERBOSE environment
variable to switch off the log_foo calls. I do sincerely hope that
this is not some new recommended way to handle LSB foo in init  
scripts.


If I'm mistaken, please point me to the docs that say what you're
doing is fine, I need to oppose that doc ;)

It's from debian-policy 9.3.5[0]. See /etc/init.d/skeleton

[0] http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.5
--
Erik Wenzel
e...@code.de







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#534562: nfdump: please reconsider VERBOSE handling in init script

2009-06-25 Thread Marc Haber
Package: nfdump
Version: 1.5.7+20081221-3
Severity: wishlist

Hi,

I usually boot my kernel with a "quiet" command line since I don't
want the system to spew screenfuls of init messages before the splash
screen takes over. This, as a - surprising - side effect causes
/lib/init/vars.sh to set the VERBOSE environment variable which in
turn causes nfdump's init script to totally silence itself. This comes
as a surprise.

IMO, the wish to have a noiseless system start does not include the
wish that an init script which may be invoked from the command line
days later does not give any feedback about its operation.

Please consider returning your init script to the behavior that is
common for init scripts, which is not honoring a VERBOSE environment
variable to switch off the log_foo calls. I do sincerely hope that
this is not some new recommended way to handle LSB foo in init scripts.

If I'm mistaken, please point me to the docs that say what you're
doing is fine, I need to oppose that doc ;)

Greetings
Marc

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.29.4-nc8000 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfdump depends on:
ii  libc6 2.9-18 GNU C Library: Shared libraries
ii  librrd2   1.2.15-0.3 Time-series data storage and displ
ii  lsb-base  3.2-22 Linux Standard Base 3.2 init scrip

nfdump recommends no packages.

nfdump suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org