hcienginestop

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf hcienginestop

  • Creator
    Topic
  • #47536
    Bill Bertera
    Participant

      I seem to remember some suggestions in the past about editting hcienginestop, has anyone done this? The problem is sometimes our shutdown scripts hang on a hcienginestop, and it either takes too long, or the process needs to be manually killed to get the script to move along.

      Anyone have any ways around this, either by editting hcienginestop or suggestions on how to call hcienginestop from ksh so it won’t hang forever?

      thanks

    Viewing 1 reply thread
    • Author
      Replies
      • #56076
        Glenn Friedenreich
        Participant

          Bill – We shortened a loop in hcienginestop (I think this was a suggestion from Charlie Bursell at a user conference) to decrease the delay in hcienginestop before it progresses to killing a stuck process – see below:

          sub waitForIt {

             local( $name ) = @_;

               local( $tries ) = 9;

        • #56077
          Tony Benitz
          Participant

            We discovered the same issue with the “hanging”.  Our solution was to take the basic program and add command line parameters to it to allow the number of loops and the wait time.

            The real issue is that you are waiting 30 seconds for 10 times for a response within the hcienginestop code.

            So now when we use hcienginestop, if you supply -s # and / or -t # it will use the command line parameters

            For example, hcienginestop -p proc_name -s 1 -t 1

            If the “nice” stop does not work, the process flow will wait one second for one loop, then start the process killing.

            Works great.

            Tony 😯

        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.