Bug#433609: Cron does not recover from broken links

Package: cron Version: 3.0pl1-100 Severity: important When there is a broken link in /etc/cron.d cron does not recognize when this link is resolved again. How to reproduce: # echo '* * * * * root /bin/true' > /root/true # ln -s /root/true /etc/cron.d/true then you see in syslog: /USR/SBIN/CRON[1

Bug#418045: sarge to etch upgrade report

Package: upgrade-reports Hello, summary: upgrade went fine, except that the network connection broke down during upgrade, see below. today I upgraded my home server from sarge to etch. This is my dialout router with the following services: ppp, postfix, firewall, apache, dns, ntp, dhcp also

Bug#402742: postinst reports db_stop: command not found

Package: clamav-daemon Version: 0.84-2.sarge.12 Installing the latest security update to clamav-daemon I get this error message: /var/lib/dpkg/info/clamav-daemon.postinst: line 163: db_stop: command not found The problem in clamav-daemon.postinst is that confmodule is only sourced if some con

Bug#367125: ext2_get_inode: bad inode number

Hello, it looks like that the latest security update to the kernel fixes this problem: http://www.debian.org/security/2006/dsa-1184 here: http://bugzilla.kernel.org/show_bug.cgi?id=6828 and here: http://www.securityfocus.com/bid/19396/info Best. -- To UNSUBSCRIBE, email to [EMAIL PROTECTE

Bug#367125: ext2_get_inode: bad inode number

Hello Goswin,On 6/16/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: Did you reboot the nfs server while clients had the fs mounted? Orstoped the nfsd and run fsck or a resize? Anything that could change the inode numbers without the clients getting any notice?Yes, we rebooted and recreated the

Bug#367125: ext2_get_inode: bad inode number

Hello,at the moment our server prints regularily like two times a minute the same message to kern.log:EXT2-fs error (device dm-5): ext2_get_inode: bad inode number: 30130240I checked and the inode really does not exist on the specified device (dm-5 is the device with minor number 5 under /dev/mappe

Bug#367125: knfsd / bad inode number on ext3

Hello, thanks for your info. That means it is a bug in ext3. It seems to ignore the errors=continue mount option, although according to the manpage it should support all the options that ext2 does. Unfortunately I'm not able to reproduce this exact behaviour, however I am able to produce a file

Bug#367125: nfs + ext3 = possible DoS

Package: kernel-image-2.6.8-2-686-smpVersion: 2.6.8-16Hello, Our central nfs-server is running Debian/Sarge and there are ~300 nfs Clients running under Debianor Solaris.  At one point we had to recreate the exported (ext3) filesystems on the server and copy the data back from backup.  Although we

Bug#309744: acknowledged by developer (Bug#309744: fixed in autossh 1.2g-2)

Hello, Debian Bug Tracking System wrote: We believe that the bug you reported is fixed in the latest version of autossh, which is due to be installed in the Debian FTP archive: will this make it into sarge? I mean it's not uploaded yet. The fix is there for over a week now... Peter

Bug#309744: fails if monitoring port = 0

Package: autossh Version: 1.2g-1 Severity: important When I turn monitoring off, either by specifying "-M 0" on the command line or by setting the environment variable AUTOSSH_PORT=0, autossh creates a garbled command line argument to ssh which in turn fails to run. This is how it looks: # autossh

Bug#303111: postinstall fails if root password is empty

Hello, the latest patch may solve this bug but introduces another one... If the root password is empty the command line turns out to be this: /usr/bin/mysqladmin -u root "" ping which results in this error: /usr/bin/mysqladmin: Unknown command: '' The solution will probably be: do in line 67: MYSQL