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

[Steve Langasek]

Hi James,

On Fri, Oct 28, 2011 at 10:03:50AM +0100, James Hunt wrote:

> > In case a job produces some insane amount of output (which could be
> > unnoticed with older Upstart) won't this fill up the disk, possibly
> > causing deny of service?
> 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 haven't looked at the code yet; is all logging done on behalf of user jobs
done with the permissions of that user?

> 3) Badly Behaved Jobs

> If a job or a daemon is producing heaps of data, that needs to be
> investigated.  The logger will expose these badly behaved jobs to allow
> them to be fixed :)

However, if user jobs are enabled and logging enabled for them, can't a user
intentionally *create* a badly behaved job?  We don't want the cost of
having better logging for system jobs to be that users can run amok.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20111028/5c425f82/attachment.pgp>