Date: Sun, 11 Dec 2005 13:50:19 GMT From: Martin Matuska <martin@matuska.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/89940: [PATCH] Client-only support for sysutils/nut Message-ID: <200512111350.jBBDoJtI076050@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/89940; it has been noted by GNATS.
From: Martin Matuska <martin@matuska.org>
To: bug-followup@FreeBSD.org
Cc: Joerg Pulz <Joerg.Pulz@frm2.tum.de>
Subject: Re: ports/89940: [PATCH] Client-only support for sysutils/nut
Date: Sun, 11 Dec 2005 14:49:38 +0100
Thank you for your patch.
Your approach is not bad, but:
in my approach, the upsmon is fully independent from the nut.sh startup script,
and in real, the program is independent, too. You do not need local upsd for
upsmon and vice versa.
Here is an example:
I have a local UPS and both scripts started (nut.sh and nut_upsmon.sh). I stop
nut.sh ->
----------
rita# /usr/local/etc/rc.d/nut.sh stop
Network UPS Tools - UPS driver controller 2.0.2
Stopping UPS: mge
rita#
Broadcast Message from root@rita
(no tty) at 14:37 CET...
Communications with UPS mge@localhost lost
----------
Then I start the script ->
----------
rita# /usr/local/etc/rc.d/nut.sh start
Starting nut.
Network UPS Tools - UPS driver controller 2.0.2
Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.64 (2.0.2)
Detected ellipse premium 1200 [unknown] on /dev/cuad0
Network UPS Tools upsd 2.0.2
Connected to UPS [mge]: mge-shut-cuad0
Synchronizing......done
Network UPS Tools upslog 2.0.2
logging status of backups@localhost to /var/log/ups.log (300s intervals)
Broadcast Message from root@rita
(no tty) at 14:39 CET...
Communications with UPS mge@localhost established
----------
As you can see, upsmon was running all the time and re-established its
connection with the local upsd. It operates indepedently.
What if my upsmon is monitoring more UPS's than only the local one?
I have such a setup on one of my systems. With your approach it would be
impossible to stop upsd or upsmon separately using startup scripts.
So I still recommend using two startup scripts.
The decision is of course in your hands :-)
Thanks,
Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512111350.jBBDoJtI076050>