Repository navigation
Replies: 2 comments
|
Thonny runs user scripts in a separate child process (the backend). If your script forks/daemonizes but doesn't detach correctly or if the parent (Thonny's backend) doesn't wait() on it, you get zombies. Since Thonny controls the lifecycle of the Python process to support debugging/stopping, it might not handle daemonized children the same way a raw shell does. Try ensuring your daemon detach logic includes os.setsid() and double-forking, or check Thonny's 'Run' options to see if 'Run in Terminal' (if available) behaves differently. |
|
Thanks for your reply. |
Uh oh!
There was an error while loading. Please reload this page.
Hello.
Why Thonny make zombie process from my daemon script?
When I starting My daemon in Debian11 with Python 3.9.2 everythink is o.k.
If I used to this Thonny interpreter , starting My daemon script = zombie process and exit with error.
System: Raspberry OS based on Debian 11.
Thonny version: 4.1.7
Python version: 3.9.2
All reactions