On Thu, 27 May 2010, Christoph Anton Mitterer wrote:
> > Thanks for the feedback, but are you really suggested to replace
> > an informative message (which points to what exactly needs to be changed)
> > with a generic 'enabled/disabled' action (whenever there is no ENABLED
> > variable at all) suggestion?
> Well,... it's a difficult question... I've seen most packages t only
> give status messages like "started", "disabled" and so on in their init
> scripts.
yeap -- and most of the time it is just that:
/etc/default/bluetooth:BLUETOOTH_ENABLED=1
/etc/default/bluetooth:HID2HCI_ENABLED=0
/etc/default/ipmievd:ENABLED=false
/etc/default/pyro-nsd:ENABLED=0
/etc/default/stunnel4:ENABLED=0
/etc/default/sysstat:ENABLED="false
> And I've seen "bug"-reports from other users regarding too chatty init
> scripts...
saw those too, and often it was simply non-conformance to use
/lib/lsb/init-functions as the way to ease the conformance with
Debian policy 9.4 Console messages from init.d scripts
> Perhaps one should discuss this at debian-devel, whether there's a best
> practise for init-script messages.
Sure -- please feel free to raise a discussion and use edac-utils as an
example ;)
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
