Yes, the job shows up when I run "atq". I also checked the syslog file and it doesn't seem to contain anything relevant to "at" command. Here is output from my shell: mike@myp:~ $ date Mon Aug 7 13:59:11 EDT 2006 mike@myp:~ $ at 14:00 warning: commands will be executed using /bin/sh at> gvim at> <EOT> job 21 at Mon Aug 7 14:00:00 2006 mike@myp:~ $ atq 21 Mon Aug 7 14:00:00 2006 a mike mike@myp:~ $ date Mon Aug 7 14:00:38 EDT 2006 mike@myp:~ $ atq root@myp:/home/mike root# tail /var/log/syslog Aug 7 13:59:12 localhost kernel: parport0: FIFO is stuck Aug 7 13:59:12 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 13:59:22 localhost kernel: FIFO write timed out Aug 7 14:00:01 localhost /USR/SBIN/CRON[17397]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1) Aug 7 14:00:33 localhost kernel: parport0: FIFO is stuck Aug 7 14:00:33 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 14:00:43 localhost kernel: FIFO write timed out Aug 7 14:01:53 localhost kernel: parport0: FIFO is stuck Aug 7 14:01:53 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 14:02:03 localhost kernel: FIFO write timed out Thanks. On 8/6/06, Florian Kulzer <florian@molphys.leidenuniv.nl> wrote:
On Fri, Aug 04, 2006 at 22:25:07 -0400, Mike Polyakov wrote:
> Hi everyone,
> My 'at' command stopped worked after kernel upgrade. Nothing seems to
> be executing at the specified time. I tried to do it as root and still
> no results. I checked that my atd daemon is running and that
> /etc/at.deny does not contain users running 'at'. Does anybody know
> why its not working?
After you schedule a job, does it show up in the queue when you run
"atq"?
After a scheduled job fails to run, are there any error messages in
/var/log/syslog?
--
Regards,
Florian
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org