commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joel Johnson <mrj...@lixil.net>
Subject [daemon] Inconsistent start/stop documentation
Date Wed, 15 Jan 2014 07:37:42 GMT
The documentation appears to be consistent for using procrun, in that 
the website [1] contains opposing on timing of when the start method 
should return.

In the description of the --StartMethod, it indicates that
     "in jvm mode, the start method should not return until
      the stop method has been called"

However, in the "Using Procrun in jvm mode" example section, it states 
that
     "Note that the method handling service start should create
      and start a separate thread to carry out the processing,
      and then return. The start and stop methods are called
      from different threads."

So which behavior is expected/preferred/required?

Joel

[1] https://commons.apache.org/proper/commons-daemon/procrun.html

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


Mime
View raw message