[
https://issues.apache.org/jira/browse/DAEMON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405081#comment-15405081
]
Mori Bellamy commented on DAEMON-259:
-------------------------------------
I was reading in jsvc-unix.c, and it looks like we register a handler so that
SIGUSR1 re-initializes the logging connection. This is workable for me right
now, but it's a little weird since the child proc (a de-escalated user) does
the re-initialization, and the logs are by default written by the parent proc
(root). so with a chmod and a postinstall script for logrotate i think i have
something that works but is a little weird.
ideally it would "just work", but maybe thats not possible ;). at least, taking
care of the permissions issue i mention above is probably an acceptable
workaround.
> still not rotate log
> --------------------
>
> Key: DAEMON-259
> URL: https://issues.apache.org/jira/browse/DAEMON-259
> Project: Commons Daemon
> Issue Type: Improvement
> Components: Jsvc
> Affects Versions: 1.0.10
> Environment: rhel-5.8, rhel-6.3
> Reporter: Levente Farkas
>
> we update to the latest commons-daemon-1.0.10, but randomly log files are not
> rotated to be more precise the rotated file created but jsvc still log into
> the old log file and the new one will be 0 length forever.
> what is the proper way, ie: how should have to look like the logrotate file
> for the jsvc log files?
> thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
