|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
The commit mentioned only fixes Mac OSX, however I have also seen this issue on CentOS 6 (or probably any other Linux or Unix) with tmpwatch installed. I would strongly recommend defaulting to /var/run/jenkins or something similar, across all *nix like OS's. The current workaround is to either edit /etc/default/jenkins to change the tmpdir (similar to the commit), or edit /etc/cron.daily/tmpwatch to exclude it as @akiko_pusu mentioned above. As I don't think the Jenkins package should be futzing with the tmpwatch cron job, it makes the most sense, in my opinion, to default to a different tmpdir location. Note that this would also require the directory to be created with the proper permissions. The /var/run/jenkins directory could be created by the package, but it should be checked and created if necessary during the init script because some OS's (Solaris) tend to mount /var/run on tmpfs.