Updated from 1.5.10.1721 to 1.5.10.1725 and FOG Multicast Manager is creating Zombies again. Will the script eventually be patched?

[Fog_Newb]

It’s this http://forums.fogproject.org/post/157404 again.

Thanks all

[Fog_Newb]

@Tom-Elliott Yes, everything is working as expected. For the longest time, FOG would always show UTC time for when an image was captured or deployed, now it is correctly showing local time and no more zombie processes! Thanks

[Tom Elliott]

@Fog_Newb Can you try pulling again?

I have made a slight change to what you performed as I’m handling this in /opt/fog/service/lib/service_lib.php under the Service_Register_Signal_handler function. This should be the central point where all the FOG Services get their base line order and configuration for starting the processes. So, from your original code, you are only applying it to MulticastManager.

While I believe that, currently, is the only service that may spawn children (due to the udpcast calls), I’m still of the mind to handle it more centrally so maybe a future process spawning thing will not need the same action.

I have pushed what i hope to fix this (using your baseline of course) and hope this hsould work for your needs.

Thank you for testing in advance and sorry for missing this before the stable release.

[Fog_Newb]

@Tom-Elliott No worries, thanks for adding that in. I’m going to update in a few to .26 and see what happens. Oh it looks like it is now showing the correct local time on captured images. I’m not sure if this started with .21, .25 or .26. Nothing changed on the system other than updating FOG. This is also excellent!

[Tom Elliott]

@Fog_Newb Does this mean things are working as you expected now?

[Fog_Newb]

@Tom-Elliott Yes, everything is working as expected. For the longest time, FOG would always show UTC time for when an image was captured or deployed, now it is correctly showing local time and no more zombie processes! Thanks