Am 28.02.2011 14:30, schrieb Michael Prokop: > Package: glusterfs-server > Version: 3.1.2-2 > Severity: normal > > > | If the status action is requested, the init script will return the > following exit status codes. > | > | 0 program is running or service is OK > | 1 program is dead and /var/run pid file exists > | 2 program is dead and /var/lock lock file exists > | 3 program is not running > | 4 program or service status is unknown > > -- > http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html > > glusterfs-server:'s init script uses 'exit 0' correctly but doesn't > support the other return codes accordingly: > > # /etc/init.d/glusterfs-server status > GlusterFS server is running.. > # /etc/init.d/glusterfs-server stop > # /etc/init.d/glusterfs-server status > GlusterFS server is not running. ... failed! > # echo $? > 1 > > whereas this should have returned with 'exit 3'. > > This means glusterfs-server can't be integrated in cluster setups > with its current initscript, see > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-lsb.html > > Switching to status_of_proc or anything similar from > /lib/lsb/init-functions might be a good idea. > > regards, > -mika- > >
may you provide a patch for this? -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: [email protected] [email protected] Comment: Always if we think we are right, we were maybe wrong. */
signature.asc
Description: OpenPGP digital signature
