You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Marko Asplund (JIRA)" <ji...@apache.org> on 2014/07/12 15:27:04 UTC
[jira] [Updated] (DAEMON-301) Communicate Daemon features more
clearly
[ https://issues.apache.org/jira/browse/DAEMON-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko Asplund updated DAEMON-301:
---------------------------------
Description:
A developer new to the subject of "daemonizing" may be left with an unclear picture of what he'd gain from using Commons Daemon with his app after reading the intro:
http://commons.apache.org/proper/commons-daemon/index.html
The features and benefits of the software could be stated in more clear terms.
Here're potential some suggestions for a list of features:
* automatically restart JVM if it dies
* enable secure shutdown of JVM process using standard OS mechanisms (Tomcat TCP based shutdown mechanism is error-prone and unsecure)
* redirect of STDERR/STDOUT and set JVM process name
* allow integration with OS init script mechanisms (record JVM process pid)
* detach JVM process from parent process and console
* run JVM and application with reduced OS privileges
* allow coordinating log file management with OS tools such as logrotate (reopen log files with signal SIGUSR1)
...
was:
A developer new to the subject of "daemonizing" may be left with an unclear picture of what he'd gain from using Commons Daemon with his app after reading the intro:
http://commons.apache.org/proper/commons-daemon/index.html
The features and benefits of the software could be stated in more clear terms.
Here're potential some suggestions for a list of features:
* automatically restart JVM if it dies
* enable secure shutdown of JVM process using standard OS mechanisms
* allow easy redirection of STDERR/STDOUT and setting JVM process name
* detach JVM process from parent process and console
* run JVM with depressed OS privileges
* record JVM process pid
...
> Communicate Daemon features more clearly
> ----------------------------------------
>
> Key: DAEMON-301
> URL: https://issues.apache.org/jira/browse/DAEMON-301
> Project: Commons Daemon
> Issue Type: Improvement
> Affects Versions: 1.0.15
> Reporter: Marko Asplund
> Priority: Minor
> Labels: docs
>
> A developer new to the subject of "daemonizing" may be left with an unclear picture of what he'd gain from using Commons Daemon with his app after reading the intro:
> http://commons.apache.org/proper/commons-daemon/index.html
> The features and benefits of the software could be stated in more clear terms.
> Here're potential some suggestions for a list of features:
> * automatically restart JVM if it dies
> * enable secure shutdown of JVM process using standard OS mechanisms (Tomcat TCP based shutdown mechanism is error-prone and unsecure)
> * redirect of STDERR/STDOUT and set JVM process name
> * allow integration with OS init script mechanisms (record JVM process pid)
> * detach JVM process from parent process and console
> * run JVM and application with reduced OS privileges
> * allow coordinating log file management with OS tools such as logrotate (reopen log files with signal SIGUSR1)
> ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)