Your message dated Tue, 16 Apr 2013 21:26:34 -0400
with message-id <[email protected]>
and subject line Re: Bug#705575: approx-gc complains about lost+found dir
has caused the Debian Bug report #705575,
regarding approx-gc complains about lost+found dir
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
705575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: approx
Version: 5.3-1
Severity: normal
In /etc/cron.weekly/approx, approx-gc complains about a lost+found dir if
present, which then generates noise from cron...
I'm thinking approx-gc should ignore the lost+found dir, as ext* filesystems
are fairly common, and it should be a reasonable setup to have
/var/cache/approx on it's own filesystem.
Alternately, providing some mechanism to ignore certain dirs in the cache might
be useful, although it seems like lost+found should be ignored by default.
Thanks!
live well,
vagrant
--- End Message ---
--- Begin Message ---
package approx
tag 705575 wontfix
thanks
> In /etc/cron.weekly/approx, approx-gc complains about a lost+found dir if
> present, which then generates noise from cron...
Please see the first question in the FAQ. I'm sorry if it's annoying,
but I don't want to add special, file-system-specific cases to the
code when it's so easy to work around this issue.
--
Eric Cooper e c c @ c m u . e d u
--- End Message ---
