commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-204) Support sending a reload message via SIGUSR2
Date Thu, 02 Jun 2011 16:33:47 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk resolved DAEMON-204.
--------------------------------

    Resolution: Fixed

Committed the modified version of your patch.
I have mostly changed its purpose to be be a generic signaling solution.
Once the signal is received it is up to the user to decide what action will be performed.
It can be like in your case a softReload or a complex failover if the SIGUSR2 represents a
OS condition (like low disk space, etc...)

Anyhow, many thanks for the patch!


> Support sending a reload message via SIGUSR2 
> ---------------------------------------------
>
>                 Key: DAEMON-204
>                 URL: https://issues.apache.org/jira/browse/DAEMON-204
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Jsvc
>         Environment: linux/unix
>            Reporter: Nick Griffiths
>            Priority: Minor
>             Fix For: 1.0.6
>
>         Attachments: soft-reloadable.diff
>
>
> I've often wanted to be able to support config reloading (like apache's or nginx's soft
reload) in our daemons, so I've been hacking around with jsvc to see how difficult it would
be to add.  It seems to have been quite easy to do it via signals (patch attached), but I'm
not confident with the low level c-stuff.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message