commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject [daemon] Documentation for DaemonConfiguration file format and SIGUSR1
Date Fri, 05 Oct 2012 23:56:37 GMT
I'm looking at using Daemon, and unless I'm just failing to find
documentation there doesn't seem to be much documentation at all on
how one would use DaemonConfiguration. From looking at it I imagine
the idea is that one specifies the name of a config file with the
-daemon-properties argument passed to jsvc or procrun and then during
init your daemon looks up the values for the properties it's defined.
However, how the pairs of strings are specified in the configuration
file appears to be undocumented.

If it would help I'd be happy to edit the wiki to add additional
documentation if someone is willing to check it's correctness after I
write it. From what I can tell from glancing at the java source code,
whenever a call is made to the one start, stop, init etc a new
instance of the class implementing Daemon is created, meaning that
some static state should be used to contain the actual per program
data. The DaemonUserSignal interface is implemented in order to
receive SIGUSR2, but there doesn't seem to be any support for SIGUSR1
or SIGHUP. Is there a reason for this?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message