I feel like the HUP should be a full server restart?
Clients don't have a way to know that they need to reload the config
file, currently. Likewise, since someone could just kill the server and
then restart with a totally different config file, I don't think that we
want to try to enforce any
Ok- just kinda checking to make sure of what you guys had in mind. If
the HUP is a full restart of the server, then it will complain on its
own if the config file doesn't match what's in the storage space, so
that isn't really a danger. It also means that pretty much any tuning
parameter is l
I have a few questions about some details of the implementation:
- What exactly will a HUP do on the server side? For example, is this
pretty much a full server restart, a restart of the I/O components
(job/trove/bmi/etc.), or just selectively reseting parameters that can
be changed dynamical
