Menu

#1876 ilo2_ribcl takes a long time to exit on kill

3.6.0
closed-fixed
dr_mohan
HP Proliant plugin
5
2015-06-16
2015-05-08
dr_mohan
No

Steps to reproduce
1. Use a dl380g9 target and stop the acpid on that target
2. Use hpipower to reset. Make sure it fails to power cycle the system.
3. As soon reset is issued, kill the openhpid on the other window.
4. It takes more than 90 seconds for the daemon to die after kill is issued

Looks like ilo2_ribcl plugin waits in a loop sleeping and checking the system if the power is off. During this cycle the plugin could check for the variable and exit if the signal is set. That way it could exit between the cycles.

Discussion

  • dr_mohan

    dr_mohan - 2015-06-10

    A global variable signal_service_thread is created to communicate the signal to the service threads. The service threads could use the variable to exit the thread. Patch is attached. Please review

     
  • dr_mohan

    dr_mohan - 2015-06-16
    • status: open --> closed-fixed
     
  • dr_mohan

    dr_mohan - 2015-06-16

    Fixed in checkin #7631