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 think
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.
___
CentOS mailing l
On Tue, 2013-01-22 at 02:36 -0800, John Doe wrote:
> From: Jerry Geis
>
> You could use a "cluster ssh" to run your commands at the same time on all
> hosts.
> You could run a script on each server that just run an infinite loop and, at
> a give time, runs a command.
IMO, if one is going to a
Am 21.01.2013 um 21:21 schrieb Jerry Geis :
> 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 inclu
On 01/21/2013 10:17 PM, Jerry Geis wrote:
>> Why do you think you need to do that and make sure they run at exactly
>> the same second? It seems like instead it would be better to make your
>> command more robust to small deviations in the time at which they are
>> run.
>>
> keith - Thanks for yo
On Mon, Jan 21, 2013 at 4:46 PM, Jerry Geis wrote:
> > @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 i
From: Jerry Geis
> So what mechanizim exists to run command down to the second?
> I'd rather not wait an entire 59 seconds to run the command.
You could use a "cluster ssh" to run your commands at the same time on all
hosts.
You could run a script on each server that just run an infinite loop a
On 01/21/2013 11:46 PM, Jerry Geis wrote:
>> @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
On Jan 21, 2013, at 16:46, Jerry Geis wrote:
> 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
>
> Why do you think you need to do that and make sure they run at exactly
> the same second? It seems like instead it would be better to make your
> command more robust to small deviations in the time at which they are
> run.
>
keith - Thanks for your reply.
I do need to run the commands at exac
On 2013-01-21, Jerry Geis wrote:
> I am looking for a way to "sync" up running a command on 10 boxes at the
> same time.
Why do you think you need to do that and make sure they run at exactly
the same second? It seems like instead it would be better to make your
command more robust to small dev
> @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
>
> @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 d
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
On Mon, Jan 21, 2013 at 3:51 PM, Joseph Spenner wrote:
> >From: Jerry Geis
>
> >To: CentOS ML
> >Sent: Monday, January 21, 2013 1:21 PM
> >Subject: [CentOS] the at command
> >
> >I was trying to use the 'at' command.
> >
> >Does it n
>From: Jerry Geis
>To: CentOS ML
>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 &
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
__
17 matches
Mail list logo
