> I have the approx cache in a separate partition, which is an ext3
> filesystem with a lost+found directory.
>
> When running approx-gc, it looks like the lost+found directory is
> stopping its execution: [...]
It is printing an error message, but it should continue
processing. This was fixed in response to bug #488115.
It just happens to be the final error message it prints, because the
last thing approx-gc does is a depth-first traversal of the cache to
remove empty directories. So /lost+found will be one of the last
ones visited.
It would be fairly ugly to add a special case just for "lost+found".
Would it be sufficient to filter out the error so you don't get email
from the cron job? Something like this should work
(in /etc/cron.weekly/approx):
/usr/sbin/approx-gc --quiet 2>&1 | fgrep -v lost+found
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
