I wrote an awesome perl plugin, and it works!

because of the awkward interface of the device which I am collecting
statistics from, I fork and collect the data asynchronously, and hand them
over to my read callback routine, which can return the data immediately.

Now, when I restart collectd, my forked process does not get killed but
keeps on running. I would like it to die properly. for that reason I need
to handle the signal properly that ends the parent process, for it to kill
the child, too, before it exists.

What is the signal that kills the perl plugin process?

kind regards!
_______________________________________________
collectd mailing list
[email protected]
https://mailman.verplant.org/listinfo/collectd

Reply via email to