Comment 3 for bug 1921154

Hello:

I'm developing a possible solution in oslo.privsep. [1] implements a privsep decorator with timeout. When the client side timeouts, the method raises a timeout exception. That can be catch by Neutron.

The problem: the commands will continue running in the daemon and nothing will stop the thread running it until the command returns. This design is unstable because we can run out of threads very quick.

A possible alternative could be to execute those commands spawning a new process, instead a new thread. This process can be monitored and, if needed, killed by the daemon if does not reply on time. But this is something that I need to propose in this patch.

Regards.

[1]https://review.opendev.org/c/openstack/oslo.privsep/+/782981