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". Thanks, Jerry
>From: Jerry Geis <geisj at pagestation.com>>To: CentOS ML <centos at centos.org> >Sent: Monday, January 21, 2013 1:21 PM >Subject: [CentOS] 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". > >Thanks, > >JerryI think you're limited to 1 minute granularity.? But if you want to run something 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 ______________________________________________________________________ If life gives you lemons, keep them-- because hey.. free lemons. "? Sticker" fixer:? http://microflush.org/stuff/stickers/heartFix.html
On 01/21/2013 03:21 PM, Jerry Geis wrote:> 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". > > Thanks, > > Jerry > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >from man at: "At allows fairly complex time specifications, extending the POSIX.2 standard. It accepts times of the form HH:MM to run a job at a spe- cific time of day. (If that time is already past, the next day is assumed.) You may also specify midnight, noon, or teatime (4pm) and you can have a time-of-day suffixed with AM or PM for running in the morning or the evening. You can also say what day the job will be run, by giving a date in the form month-name day with an optional year, or giving a date of the form MMDDYY or MM/DD/YY or DD.MM.YY or YYYY-MM-DD. The specification of a date must follow the specification of the time of day. You can also give times like now + count time-units, where the time-units can be minutes, hours, days, or weeks and you can tell at to run the job today by suffixing the time with today and to run the job tomorrow by suffixing the time with tomorrow." There is no HH:MM:SS -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registerd Linux user No #267004 https://linuxcounter.net/ ****
> @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.I am looking for a way to "sync" up running a command on 10 boxes at the same time. So I thought - hey in my program "I can send a command out that I want to run - this command is also another program of mine, get the current time, add 5 seconds to it, send this time HH:MM:SS to all 10 boxes and "schedule" an "at" command to run at that time. So all 10 boxes are running NTP and I thought it would be fine then if one box got it slightly faster than the last it would not matter as the "at" command would schedule the command to run all at the same time. So what mechanizim exists to run command down to the second? I'd rather not wait an entire 59 seconds to run the command. Thanks, Jerry
Am 21.01.2013 um 21:21 schrieb Jerry Geis <geisj at pagestation.com>:> 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".http://people.redhat.com/~rjones/whenjobs/ -- LF
Have the nodes subscribe to a Multicast server. Using Pipes, Signals, and some other basic operating system course terminology the name of which escapes me at the moment. setpriority() or nice up (-15) the priority of your software.
On 01/22/2013 01:39 PM, Rob Townley wrote:> Have the nodes subscribe to a Multicast server. > > Using Pipes, Signals, and some other basic operating system course > terminology the name of which escapes me at the moment. > > setpriority() or nice up (-15) the priority of your software.Good thinking. There should only be one hop, and make that a layer 2 hop, between the multicast server and the systems. A 10ms delay through an IP router could impact the whole sync process. Again there IS 802.1 bridging designed for this; I could look it up if needed as I once did 802.1 standards, but now do 802.15 stuff... In IPv6 you could use anycasts instead, and this is an example of what anycasts were designed for.