Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

What I want to do is the following (in wierd prototype):

main: our %ssh (hash of active ssh sessions, Net::OpenSSH) read file with list of vm's to turn off. for each line with 1 or more vm's start thread1 kill_all_thread1 after timeout for each line with 1 or more vm's start thread2 thread1: @vms = split (',',$0) for each vm gather all info needed if (! exists $ssh{vm-manager} { $ssh{vm-manager} = Net::OpenSSH->new(vm-manager) (stdout,stderr)=$ssh{vm-manager}->capture2(request vm to stop) *check errors* (status,stderr)=$ssh{vm-manager}->capture2(request status vm) while (status != dead) { (status,stderr)=$ssh{vm-manager}->capture2(request status + vm) sleep some time } thread2: @vms = split (',',$0) for each vm gather all info needed if (! exists $ssh{vm-manager} { $ssh{vm-manager} = Net::OpenSSH->new(vm-manager) (stdout,stderr)=$ssh{vm-manager}->capture2(pull plug vm)

The current solution with ksh has several problems:

  • It's all sequential.
    Not a problem with 2-3 vm's, but the total we have is 70+.
  • It initiates a new ssh session per command issued.
    When trying to split the list into seperate commands, the vm-manager gets swamped with ssh sessions. (old hardware, no budget to replace with something fast enough to handle lots of ssh logins)
  • Most vms can be stopped parallel, but some combination of vms may only be stopped in sequence. (application requirements)
  • Sometimes a vm refuses to die within the allotted time.
  • When a vm refuses to die and there are dependent vms, the nice version has to be killed and the rude version has to be started for the same set.
    I.e. in list lpar1,lpar2 when lpar1 refuses to die, it's not allowed to stop lpar2 and then kill lpar1, but it's required to kill lpar1 and then stop/kill lpar2.

Now I'm typing this, I'm thinking of relocating the timeout inside the while loop of thread1, combine thread 1 and 2 and have the resulting thread handle the stopping of it's list. When a timeout within the thread occurs, kill and be friendly with the next. (or surrender after second timeout and exit with a list of vms that have not yet been disabled.)

With the scenario above, is it possible to have a second timeout in main and just simply exit when the main timeout is reached?

$_->join for @jobs;

This waits for the threads to end, how to escape this line? As far as I can find, that's where I need the signal (and the threads->exit() in the signal handler) for.


In reply to Re^6: Perl 5.8.8 threads, clean exit by T_I
in thread Perl 5.8.8 threads, clean exit by T_I

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (3)
As of 2024-03-28 17:40 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found