I'm glad to hear that it's working for you (I basically modeled it after a BB manifest file I found somewhere) If you haven't already done so, and the improvements work in a Solaris environment (I no longer have any to test with), feel free to update the Xymonton page...it's just a wiki after all :-).
=G=
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Root, Paul Sent: Friday, November 30, 2012 10:15 AM To: 'Roland Soderstrom'; xymon at xymon.com Subject: Re: [Xymon] Solaris 10 xymon SMF
I've done the same thing with Linux and solaris init scripts.
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Roland Soderstrom Sent: Tuesday, August 28, 2012 4:48 PM To: xymon at xymon.com Subject: [Xymon] Solaris 10 xymon SMF
Hi,
There is a minor issue with the Solaris 10 SMF for xymon by Galen Johnson that I improved a bit. Thanks Galen for the nice work :D At least it works fine for us. When you disable the xymon service it could wait for up to 5 min before disabling it because the iostat and vmstat are running. (300 min)
I been trying some different approaches in the manifest but it doesn't really work properly. I had to change the default timeout (30) to 300 to cater for the 300min possible run time of iostat, vmstat. Otherwise it will go into maintenance mode. Today I had a different approach and changed the xymon.sh script instead, that worked really nice. In server/bin/xymon.sh I added these simple lines to the stop function. (works in Solaris 10)
"stop")
if test -s /usr/local/xymon/logs/xymonlaunch.pid
then
kill -TERM cat /usr/local/xymon/logs/xymonlaunch.pid
echo "Xymon stopped"
else
echo "Xymon is not running"
fi
rm -f /usr/local/xymon/logs/xymonlaunch.pid
# kill off the remaining xymon processes, ie vmstat iostat etc.
sleep 2
pkill 'iostat|vmstat' -U xymon
;;
Maybe it could help someone else out there. I'm running 4.3.10
Roland
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.