community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMDEV-162) Redirect cronjob standard output to log files
Date Thu, 15 Oct 2015 09:44:05 GMT

    [ https://issues.apache.org/jira/browse/COMDEV-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958589#comment-14958589
] 

Sebb commented on COMDEV-162:
-----------------------------

Output has been redirected to /var/log/www-data for the python cronjobs.
There are a couple of other jobs that perform svn adds; these are not yet redirected, but
there is not much output from these.

> Redirect cronjob standard output to log files
> ---------------------------------------------
>
>                 Key: COMDEV-162
>                 URL: https://issues.apache.org/jira/browse/COMDEV-162
>             Project: Community Development
>          Issue Type: Improvement
>          Components: Projects New, Reporter Tool
>            Reporter: Sebb
>
> At present, the projects.a.o and reporter.a.o cronjob output goes to the www-data mailbox.
This is getting quite large, and is not particularly easy to view as all the jobs are in the
same file.
> I think it would be more useful to redirect the output to separate log files for each
job in separate log directories e.g. under /var/logs.
> This would allow the use of logrotate to manage the log files if required.
> In order to make it easy to check the log files, it might be worth considering making
the most recent ones available via the web. I don't think there is any private information
in the logs, but this would need to be checked first.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message