Bug#679500: cron: test for missing lost+found should ignore bind mounts

2012-07-02 Thread Toby Speight
0 In article 
CAB9B7UuZKh=o-89Q35MHbwhCU2k1Fz4=xcu3qpyozoklzd4...@mail.gmail.com,
0 Javier Fernandez-Sanguino URL:mailto:j...@computer.org (Javier) wrote:

Javier This bug was already reported (in bug reports #662605 and
Javier #660879) and has been fixed in the 3.0pl1-123 version (in
Javier unstable now) by removing the standard cron task file.

Oops - sorry I didn't check thoroughly enough.

One note on the proposed fix - I think that the argument that fsck will
create /lost+found is possibly a bit flawed - the point of having a
large enough pre-created directory is to avoid any block allocations
during fsck, to reduce the risk of further corrupting the filesystem
when the free list is mangled.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#679500: cron: test for missing lost+found should ignore bind mounts

2012-06-30 Thread Javier Fernandez-Sanguino
forcemerge 660879 679500
forcemerge 660879 662605
thanks

On 29/06/2012, Toby Speight t.m.speight...@cantab.net wrote:
 Every day, I receive an email warning me about missing lost+found
 directories.  But the filesystems listed are merely bind mounts of
 sub-trees of other filesystems which do in fact have lost+found.  I
 think that the test script should filter out bind mounts before
 checking for /lost+found.

This bug was already reported (in bug reports #662605 and #660879) and
has been fixed in the 3.0pl1-123 version  (in unstable now) by
removing the standard cron task file.

I'm merging this bug report with the previous bug reports (and thus
closing this one too)

Regards

Javier



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#679500: cron: test for missing lost+found should ignore bind mounts

2012-06-29 Thread Toby Speight
Package: cron
Version: 3.0pl1-121
Severity: normal
File: /etc/cron.daily/standard

Dear Maintainer,

Every day, I receive an email warning me about missing lost+found
directories.  But the filesystems listed are merely bind mounts of
sub-trees of other filesystems which do in fact have lost+found.  I
think that the test script should filter out bind mounts before
checking for /lost+found.


-- Package-specific info:
--- EDITOR:


--- /usr/bin/editor:
/usr/bin/emacs23-x

--- /usr/bin/crontab:
-rwxr-sr-x 1 root crontab 40912 Jan 30 11:09 /usr/bin/crontab

--- /var/spool/cron:
drwxr-xr-x 5 root root 4096 Dec  6  2007 /var/spool/cron

--- /var/spool/cron/crontabs:
drwx-wx--T 2 root crontab 4096 Apr 13 22:53 /var/spool/cron/crontabs

--- /etc/cron.d:
drwxr-xr-x 2 root root 4096 Jun  5 11:05 /etc/cron.d

--- /etc/cron.daily:
drwxr-xr-x 2 root root 4096 Jun 26 09:43 /etc/cron.daily

--- /etc/cron.hourly:
drwxr-xr-x 2 root root 4096 Feb 10 13:59 /etc/cron.hourly

--- /etc/cron.monthly:
drwxr-xr-x 2 root root 4096 Feb 10 13:59 /etc/cron.monthly

--- /etc/cron.weekly:
drwxr-xr-x 2 root root 4096 Jun  1 17:58 /etc/cron.weekly



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armel

Kernel: Linux 3.2.9-balti (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cron depends on:
ii  adduser 3.113+nmu3
ii  debianutils 4.3.1
ii  dpkg1.16.3
ii  libc6   2.13-33
ii  libpam-runtime  1.1.3-7.1
ii  libpam0g1.1.3-7.1
ii  libselinux1 2.1.9-5
ii  lsb-base4.1+Debian7

Versions of packages cron recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.80-3

Versions of packages cron suggests:
pn  anacronnone
pn  checksecurity  none
ii  logrotate  3.8.1-4

Versions of packages cron is related to:
pn  libnss-ldap   none
pn  libnss-ldapd  none
pn  libpam-ldap   none
pn  libpam-mount  none
pn  nis   none
pn  nscd  none

-- Configuration Files:
/etc/default/cron changed:
READ_ENV=yes
EXTRA_OPTS=-L 12


-- no debconf information