Bug#208010: [PROPOSAL] init script LSB 1.3 compliance
- To: 208010@bugs.debian.org
- Cc: Martin Godisch <martin@godisch.de>
- Subject: Bug#208010: [PROPOSAL] init script LSB 1.3 compliance
- From: Andreas Barth <aba@not.so.argh.org>
- Date: Mon, 1 Sep 2003 09:35:46 +0200
- Message-id: <[🔎] 20030901073546.GC29459@mails.so.argh.org>
- Reply-to: Andreas Barth <aba@not.so.argh.org>, 208010@bugs.debian.org
- In-reply-to: <20030831202903.GA871@quetzlcoatl.dodds.net>
- References: <20030831111138.GA20044@carlos.godisch.de> <20030831135357.GB29788@grep.be> <20030831111138.GA20044@carlos.godisch.de> <20030831130803.GB24723@doc.ic.ac.uk> <20030831170718.GA4095@carlos.godisch.de> <20030831175623.GE19174@quetzlcoatl.dodds.net> <20030831182902.GA5295@carlos.godisch.de> <20030831202903.GA871@quetzlcoatl.dodds.net>
* Steve Langasek (vorlon@netexpress.net) [030831 22:35]:
> Without the 'exit 5' portion, I think it represents a good target to
> work towards; but it's a little too early to try to mandate these
> fine-grained exit codes in policy. I don't see anything in policy that
> says you can't use most LSB exit codes from init scripts today -- if
> there is, we should probably remove it -- so it's better to first try
> implementing this in a few packages before making it part of policy.
It would perhaps be good if the policy states exactly which exit codes
are allowed and which are preffered. That would make implementing
easier (perhaps this part should be in the developer reference, where
it would also help).
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Reply to: