[Nut-upsdev] Autodetecting running drivers by the 'upsd' server

Daniel O'Connor doconnor at gsoft.com.au
Wed Jun 6 12:41:59 UTC 2007

On Wednesday 06 June 2007 21:18, Arjen de Korte wrote:
> > The server could periodically look for new sockets (and/or on
> > SIGHUP).
> I'm not in favor of periodically looking for new sockets. If you
> don't start additional drivers, it is pointless to check for new
> sockets regularly. A better option would be for the drivers to send a
> SIGHUP to the server on startup (if a 'upsd.pid' file is found),
> which we already honor. The prerequisite that drivers and server are
> running under the same UID is satisfied most of the time (if not
> always) anyway, since they will have to communicate to one another.
> The bonus here is, that we might send a SIGHUP to the server on
> intentional termination of the driver too, so that it wouldn't be
> checking for stale sockets forever. This opens the way for true
> hot(un)plugging of drivers.

Sounds like a good plan to me!

Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070606/7ec827a9/attachment.pgp 

More information about the Nut-upsdev mailing list