Closed jouvin closed 10 years ago
After more checks, it seems this problem affects more SL5 systems than SL6 ones, without being completely clear. It seems to be pretty systematic on SL5. Is it something related to YUM as this restart (with the resulting ncm-ncd kill) happens as part of the RPM post install script? What I observed is that ncm-ncd will shutdown at some point but it can be matter of 10-15 mn...
This issue should be reviewed when #9 has been released. If delayed processing of TERM
signal works as expected, this should not happen anymore as ncm-ncd
will not be killed.
ok to test
When ncm-cdispd is upgraded, it restarts. Sometimes, on some machines, ncm-ncd doesn't shut down quickly enough and this prevent ncm-cdispd to run ncm-ncd again (lock file present). When a new profile is notified later but without another change, it doesn't trig reexecuting the components that failed to run when ncm-ncd was running.