Xymon Mailing List Archive search

Request change for init.d/xymon-client

3 messages in this thread

list Grégory Bulot · Wed, 04 Jan 2017 12:07:18 +0100 ·
Hi,

Because i'm using xymon also in the master host in lxc (with debian), so
"ps" show all xymonlaunch used inside containers.

start-stop-daemon answer "already running"

Is it possible to change /etc/init.d/xymon-client, like that :
22a23
DAEMONNAME=xymonhyperv
51c52
<       start-stop-daemon --exec $DAEMON --chuid xymon --umask 022
--start \
---
      start-stop-daemon --name $DAEMONNAME --exec $DAEMON --chuid
xymon --umask 022 --start --pidfile=$PIDFILE \

and the man say
" Veuillez noter qu'à moins d'utiliser --pid ou --pidfile, le programme
start-stop-daemon se comporte comme killall(1). start-stop-daemon
recherche dans le tableau des processus tout pro‐ cessus  qui
correspond  au  nom,  pid parent, uid et/ou gid du processus (si 
indiqué). Toute correspondance empêchera --start de démarrer le démon. 
Tous les processus qui correspondent recevront le signal TERM (ou le 
signal indiqué par --signal ou --retry)
"
list Axel Beckert · Wed, 4 Jan 2017 13:24:36 +0100 ·
Dear Grégory,
quoted from Grégory Bulot

On Wed, Jan 04, 2017 at 12:07:18PM +0100, Grégory Bulot wrote:
Because i'm using xymon also in the master host in lxc (with debian), so
"ps" show all xymonlaunch used inside containers.
is the LXC-guests running host Debian or are the guests themselves
running Debian?
quoted from Grégory Bulot
start-stop-daemon answer "already running"

Is it possible to change /etc/init.d/xymon-client, like that :
As far as I can see, Xymon itself only ships init scripts inside the
packaging for several distributions:

$ als xymon_4.3.27.orig.tar.gz | fgrep init
-rw-rw-r-- rpmbuild/rpmbuild  1885 2016-01-27 22:12 xymon-4.3.27/rpm/xymon-client.init
-rw-rw-r-- rpmbuild/rpmbuild  1313 2016-01-27 22:12 xymon-4.3.27/rpm/xymon-init.d
-rw-rw-r-- rpmbuild/rpmbuild  1406 2011-03-08 14:05 xymon-4.3.27/debian/init-common.sh
-rw-rw-r-- rpmbuild/rpmbuild  2514 2011-03-08 18:20 xymon-4.3.27/debian/xymon-client.init
-rw-rw-r-- rpmbuild/rpmbuild  2278 2011-03-08 18:20 xymon-4.3.27/debian/xymon.init
-rw-rw-r-- rpmbuild/rpmbuild   1360 2011-03-08 18:20 xymon-4.3.27/xymond/etcfiles/rrddefinitions.cfg

So do you use xymon-client as available in stock Debian or do you use
Xymon from https://sourceforge.net/projects/xymon/files/Xymon/?
quoted from Grégory Bulot
22a23
DAEMONNAME=xymonhyperv
51c52
<       start-stop-daemon --exec $DAEMON --chuid xymon --umask 022
--start \
---
     start-stop-daemon --name $DAEMONNAME --exec $DAEMON --chuid
xymon --umask 022 --start --pidfile=$PIDFILE \
These first start-stop-daemon line looks a lot like coming from the
init script from xymon-client as packaged in Debian 8 Jessie.

Please report issues with official Debian packages always via the
Debian Bug-Tracking system (c.f. https://bugs.debian.org/) as it might
be a debian-specific bug like I suspect in this case. At least the
init script distributed with Debian's xymon-client package is
debian-specific.

In this case you don't need to do that anymore as someone else already
did: https://bugs.debian.org/819976

The bug is also already fixed in Debian Testing (although slightly
different than you fixed it) and the fix will be part of the next
Debian Stable release expected somewhen in summer this year.

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | user-bc188e45dae4@xymon.invalid  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | user-0064bde8d49d@xymon.invalid (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)
list Grégory Bulot · Wed, 04 Jan 2017 13:42:53 +0100 ·
Bonjour,

Le Wed, 4 Jan 2017 13:24:36 +0100 "Axel Beckert" à écrit
quoted from Axel Beckert

is the LXC-guests running host Debian or are the guests themselves
running Debian?
Both are in Debian/Jessie
quoted from Axel Beckert

In this case you don't need to do that anymore as someone else already
did: https://bugs.debian.org/819976
you are right, this ticket is 100% my situation. I forgot to look
there before posting, sorry.