On Thu, Mar 22, 2012 at 12:30:47AM +, Steve Allison wrote:
> > Why are you using -E in the grep call here? $DEV should not contain any
> > regular expression, it's just a device name.
>
> An oversight on my part.
Ok. Understood.
> Same patch below with -E removed. Don't mind if it doesn'
Why are you using -E in the grep call here? $DEV should not contain any
regular expression, it's just a device name.
An oversight on my part.
I was originally trying to make sure I don't match together "/dev/foo"
and "/dev/foobar" using regex but I got conflicted output between bash
and
On Wed, Mar 21, 2012 at 08:35:27AM +, Steve Allison wrote:
> As suggested, this can be avoided by not checking the same filesystem twice.
Hi,
Thanks for the patch. Even though we are going to probably drop the
lost+found check in the near future we can consider this patch.
I have some quest
As suggested, this can be avoided by not checking the same filesystem twice.
--- standard_3.0pl1-121 2012-03-21 08:34:12.339516047 +
+++ standard2012-03-21 08:34:02.111770395 +
@@ -10,6 +10,7 @@
cd /
LOCKFILE=/var/lock/cron.daily
LOFO=lost+found
+SEENFS=""
# When flock is availab
Package: cron
Version: 3.0pl1-120
Severity: normal
/etc/cron.daily/standard:
Some local file systems lack a lost+found directory. This means if the
file system is damaged and needs to be repaired, fsck will not have
anywhere to put stray files for recovery.
5 matches
Mail list logo
