On Mon, Apr 26, 2010 at 03:02:38PM +0200, Christian Kastner wrote:
> >>> I'm guessing this is the problem - it reads the change once (after the
> >>> file's timestamp/size change), it barfs, and then it keeps ignoring the
> >>> unchanged file with a broken line until you touch it again.
> >> Yes. This is a side effect of a power-management-related feature,
> >> indented to reduce disk spin-ups on laptops.
> > This is then a horrible side-effect. If there is a fatal error in
> > user-generated data, be it a security issue or a typo, the admin *needs* to
> > be told about it. It is more important to tell them than it is to conserve
> > battery power, even on laptops.
>
> The admin *is* told about it.
>
> If you don't have anything in your logs, this would be a separate issue
> from the OP's, and I would ask you to file a new bug with
> severity:important.
>
> It doesn't have to happen every minute, but
> > at the very least there can be a daily job that sends the list of broken
> > crontabs to the root mailbox.
>
> If you consider one warning for a fatal error insufficient, please file
> a new wishlist bug so I can track the OP's bug here.
I don't think the OP's bug is any different. He could have corrected the
error e.g. by what I did - by moving a backup file into place, but then
crond didn't pick up the 'new' file because it wasn't really new.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
