Startup enhancements to avoid loosing ncm-cdispd

[jouvin]

...the profile

(in startup script and in monitoring cron job)

• Create daemon lock file whatever is the startup status to ensure that the cron job will restart it in case of a failure during installation.

[piojo-zz]

Looks good to me. I only need some clarifications in the postinstall scriptlet.

Thanks!

[jouvin]

In fact, you suggested me this fix! And it was a good suggestion.

The point is that we want to avoid at any price to have ncm-cdispd left in a state it cannot be restarted. Thus the reason for the cron job I added a couple of months ago. But when upgrading from CCM 2.2 to 3.x I killed ncm-cdispd because CCM was returning an empty profile (because the .fmt file was missing and it was probably interpreted as JSON). As a result ncm-cdispd was crashing. My feeling is that ccm-fetch --force is harmless but helps to ensure that ware a not killing ourselves only because of something wrong that happened to the cached profile.

Note that the problem mentioned above was really bad because cdp-listend would never fix it. The profile was considered already there and thus not reloaded. Only a new profile would at the end allow ncm-cdispd to restart (thanks to the cron). But this is very hard to troubleshoot and can lead to a sysadmin loosing its time and its nerves!

Michel

[piojo-zz]

Thanks for the explanation. Merging, then.