Package: at Version: 3.1.10.2 Severity: important
This is not the first time I see this bug. Now I caught it in crime scene, so it is time to expose its sins with these pieces of evidence: I forgot to run "apt-get clean" for too long and my /var beacame full. During that state this cronjob was run many times: 0,15,30,45 * * * * echo 'fetchmail -s > /dev/null 2>&1' | batch > /dev/null 2>&1 This is how my /var/spool/cron/atjobs looks like now: -=*[ROOT ZSH]*=- r...@juhtolv:/root # ls -la /var/spool/cron/atjobs total 52 drwxrwx--T 2 daemon daemon 4096 2009-07-26 13:47 ./ drwxr-xr-x 5 root root 4096 2007-08-01 11:44 ../ -rwx------ 1 juhtolv daemon 0 2009-07-26 06:30 b10e0d013d87b2* -rwx------ 1 juhtolv daemon 0 2009-07-26 06:45 b10e0e013d87c1* -rwx------ 1 juhtolv daemon 0 2009-07-26 07:00 b10e0f013d87d0* -rwx------ 1 juhtolv daemon 0 2009-07-26 07:15 b10e10013d87df* -rwx------ 1 juhtolv daemon 0 2009-07-26 07:30 b10e11013d87ee* -rwx------ 1 juhtolv daemon 0 2009-07-26 07:45 b10e12013d87fd* -rwx------ 1 juhtolv daemon 0 2009-07-26 08:00 b10e13013d880c* -rwx------ 1 juhtolv daemon 0 2009-07-26 08:15 b10e14013d881b* -rwx------ 1 juhtolv daemon 0 2009-07-26 08:30 b10e15013d882a* -rwx------ 1 juhtolv daemon 0 2009-07-26 08:45 b10e16013d8839* -rwx------ 1 juhtolv daemon 0 2009-07-26 09:00 b10e17013d8848* -rwx------ 1 juhtolv daemon 0 2009-07-26 09:15 b10e18013d8857* -rwx------ 1 juhtolv daemon 0 2009-07-26 09:30 b10e19013d8866* -rwx------ 1 juhtolv daemon 0 2009-07-26 09:45 b10e1a013d8875* -rwx------ 1 juhtolv daemon 0 2009-07-26 10:00 b10e1b013d8884* -rwx------ 1 juhtolv daemon 0 2009-07-26 10:15 b10e1c013d8893* -rwx------ 1 juhtolv daemon 0 2009-07-26 10:30 b10e1d013d88a2* -rwx------ 1 juhtolv daemon 0 2009-07-26 10:45 b10e1e013d88b1* -rwx------ 1 juhtolv daemon 654 2009-07-26 11:00 b10e1f013d88c0* -rwx------ 1 juhtolv daemon 654 2009-07-26 11:15 b10e20013d88cf* -rwx------ 1 juhtolv daemon 654 2009-07-26 12:00 b10e21013d88fc* -rwx------ 1 juhtolv daemon 652 2009-07-26 12:15 b10e22013d890b* -rwx------ 1 juhtolv daemon 654 2009-07-26 12:30 b10e23013d891a* -rwx------ 1 juhtolv daemon 654 2009-07-26 12:45 b10e24013d8929* -rwx------ 1 juhtolv daemon 652 2009-07-26 13:00 b10e25013d8938* -rwx------ 1 juhtolv daemon 654 2009-07-26 13:15 b10e26013d8947* -rwx------ 1 juhtolv daemon 654 2009-07-26 13:30 b10e27013d8956* -rwx------ 1 juhtolv daemon 654 2009-07-26 13:45 b10e28013d8965* -rw------- 1 daemon daemon 6 2009-07-26 13:45 .SEQ Now that batch queue do not move at all. I need to remove all those zero-sized files from that spool to get it back in working state. I think batch and at need some kind of sanity-check in order to prevent this bug happening. If file in that spool is empty, ignore it and move to the next file job in queue. Also user could be warned with E-Mail. There coul be also such option that simply removes all zero-sized batchjobs without warning or error messages. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (1001, 'testing'), (990, 'stable'), (500, 'proposed-updates') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages at depends on: ii libc6 2.9-12 GNU C Library: Shared libraries ii libpam0g 1.0.1-9 Pluggable Authentication Modules l ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip ii postfix [mail-transport-agen 2.6.2~rc1-1 High-performance mail transport ag at recommends no packages. at suggests no packages. -- no debconf information -- Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv "ore wo mitsumeteiru anata sama wa ossharu bakari. kesshite dakiyosete wa kurenai ooki na anata no te. ore no tanjoubi ni wa ai wo kai ataeru. kyou wa kumori nochi ame." Dir en grey -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
