From: lyrics Date: 2009-01-15T19:09:02+09:00 Subject: Re: Net::SSH serialized commands On 15 jan, 10:41, lyrics wrote: > On 15 jan, 00:30, "Sebastian W." wrote: > > > > > lyrics wrote: > > > On 14 jan, 23:31, "Sebastian W." wrote: > > > >> > end > > >> up an aggregated event loop, and then run it with the "loop" method. > > > >> -- > > >> Posted viahttp://www.ruby-forum.com/. > > > > Basically, I just want to manage 2 PCs. > > > "sending command to PC1 > > > wait until command finished > > > sending command to PC2 > > > wait until command finished > > > sending command to PC1 > > > wait until command finished" > > > > I thought open both sessions at the same time was a convenient way to > > > open them only once. > > > Hm...I'm not an expert, but it seems to me in this case that it'd be > > easier actually just to code it that way. > > > If your commands are short, you could always inline them with a {} style > > block instead of do/end, if you really want to cut down on your line > > count. :) > > > I guess for establishing the sessions, maybe it's a little inefficient > > since you're opening up four sessions instead of two, but sometimes you > > just have to DTSTTCPW. :P > > -- > > Posted viahttp://www.ruby-forum.com/. > > I may try this, but I want to avoid since this code is executed more > than 200 times. I did more test. I found out that I was working on the wrong issue: the "exec!" command do it job well. I think my issue comes from restarting a service. It likes it takes times before really "up" whereas the command returns.