Mailing-List: contact commits-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Date: Thu, 12 Nov 2015 14:36:11 +0000 (UTC)
From: "Sebb (JIRA)" <jira@apache.org>
To: commits@community.apache.org
Message-ID: <JIRA.12896566.1443259131000.50185.1447338971064@Atlassian.JIRA>
In-Reply-To: <JIRA.12896566.1443259131000@Atlassian.JIRA>
References: <JIRA.12896566.1443259131000@Atlassian.JIRA>
 <JIRA.12896566.1443259131201@arcas>
Subject: [jira] [Resolved] (COMDEV-162) Redirect cronjob standard output to
 log files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sebb resolved COMDEV-162.
-------------------------
    Resolution: Fixed

> 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)