openrc: make exit codes comply with Linux Standard Base
On Saturday, January 08, 2011 18:51:36 Eray Aslan wrote:
> The trivial patch below makes openrc comply with LSB. I am not aware of
> any service depending on the changed behaviour.
this belongs in bugzilla, not the gentoo-dev mailing list
-mike
01-08-2011, 09:21 PM
Eray Aslan
openrc: make exit codes comply with Linux Standard Base
On Sat, Jan 08, 2011 at 05:09:21PM -0500, Mike Frysinger wrote:
> this belongs in bugzilla, not the gentoo-dev mailing list
Well, this is the upstream ML but anyway, no big deal:
https://bugs.gentoo.org/show_bug.cgi?id=351160
--
Eray Aslan
Developer, Gentoo Linux eras <at> gentoo.org
01-08-2011, 09:43 PM
Mike Frysinger
openrc: make exit codes comply with Linux Standard Base
On Saturday, January 08, 2011 17:21:18 Eray Aslan wrote:
> On Sat, Jan 08, 2011 at 05:09:21PM -0500, Mike Frysinger wrote:
> > this belongs in bugzilla, not the gentoo-dev mailing list
>
> Well, this is the upstream ML
which might be relevant if we were talking about a project dedicated to a
package or two, but we arent. this is a general distro development list, not
random sub-projects that happen to come out of it. same goes for sandbox, or
catalyst, or genkernel, or crossdev, or gli, or ...
also, nowhere in the openrc package does it indicate the gentoo-dev mailing
list should be used for reporting. it does say explicitly to use bugs.g.o
though. it also mentions Roy's old site, but i'll fix that.
-mike
01-08-2011, 10:51 PM
Eray Aslan
openrc: make exit codes comply with Linux Standard Base
Linux Standard Base[1] states that for init scripts:
* status command for a stopped service should have a return code of 3
* starting an already started service or stopping an already stopped
service should be considered as successful
The trivial patch below makes openrc comply with LSB. I am not aware of
any service depending on the changed behaviour.
Use case: One can use Gentoo init scripts with cluster management
software - such as sys-cluster/pacemaker - instead of writing a resource
agent or trying to work around their limitations for each managed
service.