Hello Mario, > I have the same version installed here and I can't agree that this bug > exists, I tested it here on my local machine in the office: > > [EMAIL PROTECTED]:~$ at 11:40 > warning: commands will be executed using /bin/sh > at> echo test | mail [EMAIL PROTECTED] > at> <EOT> > job 1 at Mon Apr 16 11:40:00 2007 > [EMAIL PROTECTED]:~$ atq > 1 Mon Apr 16 11:40:00 2007 a mario > > Exactly on time the command was executed (as I can see in > /var/log/mail.log) so I think you use the program in a wrong way?! > Maybe you forgot to finish scheduling the job with Ctrl+D.
No, I used at in the same way as I did before under sarge. My favourite way to execute the at command is something like this: for host in <list>; do ssh -l root $host 'echo "shutdown -r +5" | at 16:43'; done This works on sarge, but fails on etch. I can see that the job starts running, because the output of atq changes from "1 Sun Apr 15 16:43:00 2007 a root" to "1 Sun Apr 15 16:43:00 2007 = root", but the job is not completed and stays in the queue. Regards Christoph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
