[
https://issues.jenkins-ci.org/browse/JENKINS-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160605#comment-160605
]
dogfood commented on JENKINS-5784:
----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[jenkins_main_trunk #1606|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1606/]
[FIXED JENKINS-5784] (Revision 8fb2f5162e499b5c0c4dc8f88af761b7c490bc38)
Result = SUCCESS
Kohsuke Kawaguchi :
[8fb2f5162e499b5c0c4dc8f88af761b7c490bc38|https://github.com/jenkinsci/jenkins/commit/8fb2f5162e499b5c0c4dc8f88af761b7c490bc38]
Files :
* changelog.html
* rpm/SOURCES/jenkins.logrotate
> Usage of kill in logrotate script is non-portable
> -------------------------------------------------
>
> Key: JENKINS-5784
> URL: https://issues.jenkins-ci.org/browse/JENKINS-5784
> Project: Jenkins
> Issue Type: Bug
> Components: other
> Reporter: rombert
> Attachments: hudson.logrotate.patch2010-10-20pdurbin,
> jenkins-logrotate.patch
>
>
> The logrotate script uses
> {code}kill -SIGALRM `cat /var/run/hudson.pid`{code}
> which works fine for the bash builtin, but fails for /bin/kill, which only
> accepts
> {code}usage: kill [ -s signal | -p ] [ -a ] pid ...
> kill -l [ signal ]{code}
> on CentOS 5.
> Using kill -s SIGALRM would make both variants happy and increase portability.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
