Re: Using "at" command
- From: R C V <rssv99@xxxxxxxxx>
- Date: Thu, 27 Mar 2008 16:55:20 -0700 (PDT)
It works when I pipe the command to 'at'
so $ date | at now + 2 minutes works well.
but
a) $ ls -l | at now + 2 minutes accepts the job, but gives a very
strange output in /var/spool/mail/root....
b) $killall <exec name> | at now + 2 minutes results in killall
getting executed immediately...
Am I missing something while using 'at' with those commands which have
some parameters/switches.
Also how do I get the output on the screen instead of .../mail/root..
Thanks,
R C
On Mar 26, 2:41 pm, R C V <rss...@xxxxxxxxx> wrote:
hello,
I wanted to schedule jobs to start within a space of few
seconds of each other. But 'at' is giving me a resolution of 'min'.
So I decided to put all tasks in a file and invoke
at -f <filename>
The contents of the <filename> are:
at now+1 minute "ls -l"
at now+2 minute "date"
But I get a error "Garbled time"
Can you tell me what is wrong here..Also is it possible to give
interval in seconds.
TIA,
R C
.
- Follow-Ups:
- Re: Using "at" command
- From: Bit Twister
- Re: Using "at" command
- References:
- Using "at" command
- From: R C V
- Using "at" command
- Prev by Date: Re: Wireless tools
- Next by Date: Need help in 'at' command
- Previous by thread: Re: Using "at" command
- Next by thread: Re: Using "at" command
- Index(es):
Relevant Pages
|