[PATCH] Add 'log' argument to 'console' stanza allowing job output to be captured.

[Jacek Konieczny]

On Fri, Oct 28, 2011 at 10:03:50AM +0100, James Hunt wrote:
> > Any log rotation procedure?
> There are already tools such as logrotate(8) that handle log rotation. By default Upstart will write
> system logs to /var/log/upstart/ so logrotate can be configured to deal with logs in that directory
> appropriately.

Is there a way to signal upstart to reopen the logs, so new files are
properly written after logrotate moves old ones?

> There are 3 issues here: disk, memory and badly behaved jobs:
> 
> 1) Disk
> 
> Yes it would be possible for a job to fill a disk (partition). But that's true of any application
> that can write to disk and has sufficient quota. Again, that's where tools like logrotate help, and
> having servers with separate disk partitions to avoid a major impact on other system aspects.

I understand that. I was only worried about that 'on by default' change,
which could unexpectedly cause such problems on 'previously working'
(although probably misconfigured) system. Not that I think it is a
critical problem, just

> By the way, the intention is for a follow-on patch to add the ability to specify something like:
> 
>   console log output
> 
> Such that all job output would be logged *and* sent to the console.

Looks great :)

> Thanks for your comments. It is worth stating that this feature allows Upstart to write files, which
> it has *never* done before. So, we do need to be consider all the edge cases carefully.

I can imagine. Such 'a simple thing' as writing files can be tricky,
indeed.

Greets,
        Jacek