On Mon, Jan 21, 2013 at 3:51 PM, Joseph Spenner <joseph85750@xxxxxxxxx>wrote:
> >From: Jerry Geis <geisj@xxxxxxxxxxxxxxx>
>
> >To: CentOS ML <centos@xxxxxxxxxx>
> >Sent: Monday, January 21, 2013 1:21 PM
> >Subject: the at command
> >
> >I was trying to use the 'at' command.
> >
> >Does it not have "resolution" to the second?
> >
> >When I run it with 'at -f /tmp/tt.sh "01/21/2013 15:20:45"
> >syntax error. Last token seen: 15:20
> >Garbled time
> >
> >How do I run a command in the future including "seconds".
> >
>
@Jerry:
You might explain what it is you are attempting to do or why it is you need
to schedule a job down to the second.
> >Thanks,
> >
> >Jerry
>
> I think you're limited to 1 minute granularity. But if you want to run
> something
Yes, both cron and at can be scheduled down to the minute (but no further).
And for most jobs/situations, running every minute or every couple of
minutes is suitable.
> at a specific second (ie: 13 seconds after the minute), you could modify
> the script to sleep for 13 seconds before running and run it on the minute,
> or prepend a sleep in the cron entry itself:
>
> * * * * * sleep 13; touch /tmp/foo
>
@Joseph:
Nifty trick/hack! ;)
>
> ______________________________________________________________________
> If life gives you lemons, keep them-- because hey.. free lemons.
> "♥ Sticker" fixer: http://microflush.org/stuff/stickers/heartFix.html
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
--
---~~.~~---
Mike
// SilverTip257 //
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
