Bug#706822: just make it quiet
On Sun, May 26, 2013 at 07:44:08PM +0200, Arno Töll wrote:
> On 26.05.2013 06:50, Adam Borowski wrote:
> > What about just removing the error message, at least when ran from a
> > logrotate cronjob?
> What would you suggest? I'm not at all opposed in a patch pleasing all
> of you, but I don't know one making all of you happy which is not only
> hiding problems.
Hmm, good point, this has a chance of actually hiding problems. Outside of
vserver and similar environments, root is root, period -- so a failure here
means something is terribly bad.
I wonder, perhaps we could have a failure produce a nice user-friendly
message that points to relevant documentation. Ie, if $ULIMIT_MAX_FILES
returns an error, you can write some pointers to stderr, for cron's sake.
It _will_ require manual action, but at least little time will be wasted,
either by you or the admin in question.