/var/log/yum.log gets owned by root. assertion fails, lumberjack aborts. about logstash-forwarder

[jordansissel]

Many of the current assertions were mostly for safety while writing lumberjack early.

I'm happy to replace some of those insist calls with log calls instead. ;)

[ChrisLundquist]

Replacing that with a warning would take care of it.

In the 30 minutes that I have been thinking about this, my best answer to the permissions problem is to start as user X (root), open files for reading, then fork and drop privileges as user Y (lumberjack).

That is a fairly large change (implement daemonizing and dropping privileges) but I can't think of a better way at the moment.

[ChrisLundquist]

same perms issue with /var/log/messages and /var/log/secure

[jordansissel]

you can work around this by fixing the permissions on the file, fwiw, and is a much more explicit and practiced access control model than is running as root and, as a new piece of software, promising to only doing the things claimed ;)

[ChrisLundquist]

Fair enough. I haven't tested if someone changes the permissions back on those files like yum does. I don't really want chef to fight RHEL on log permissions.

[jordansissel]

Lumberjack should now no longer fail if it cannot read a file.