You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Bill Stewart (JIRA)" <ji...@apache.org> on 2019/06/13 13:14:00 UTC

[jira] [Issue Comment Deleted] (DAEMON-259) still not rotate log

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

Bill Stewart updated DAEMON-259:
--------------------------------
    Comment: was deleted

(was: SIGUSR1 doesn't exist on Windows. What about providing the option to disable all procrun logging and let application/servlet container/etc. handle stdout/stderr logging? IMO it is very confusing that procrun does its own "non-rotatable" logging and prevents stdout/stderr logging from Java altogether.)

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)