duct.py | pj | |
---|---|---|
4 | 1 | |
107 | 2 | |
- | - | |
1.8 | 10.0 | |
about 2 years ago | over 4 years ago | |
Python | C | |
MIT License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
duct.py
Posts with mentions or reviews of duct.py.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-06.
-
The GNU C Library version 2.39 Released
Notably, this adds the new pidfd_spawn, pidfd_spawp, and pidfd_getpid functions, which should fix the PID race problem, as discussed here: <https://github.com/oconnor663/duct.py/blob/master/gotchas.md...>
- Proper way to spawn detached process
- Duct – Child process gotchas, bugs, and platform inconsistencies
-
Sending signals to Unix process groups
If anyone can suggest an update to https://github.com/oconnor663/duct.py/blob/master/gotchas.md..., please let me know. As far as I'm aware, there's still no reliable way to kill a tree of processes on Unix that's suitable for library code.
pj
Posts with mentions or reviews of pj.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-06.
-
Sending signals to Unix process groups
I wrote a 'subreaper' program to capture and kill such things some time ago. It's pretty basic, having options to pass on signals, start killing subprocesses if it receives a signal, or killing subprocesses after the initial subprocess dies. There is an undocumented --all that prints logs, kills on stats and doesn't start killing when the main program dies. I use it for killing test subprocesses or capturing things to terminals that would otherwise double-fork out of them, allowing me to kill them and all their subprocesses with a ctrl-c.
https://github.com/knome/pj
>Linux is in the middle of adding new APIs like pidfd_send_signal, but none of them are aimed at improving the situation with grandchildren.
While my subreaper is vulnerable to pid reuse, but I think it could be fixed by having it do this:
loop
What are some alternatives?
When comparing duct.py and pj you can also consider the following projects:
shadow - Shadow is a discrete-event network simulator that directly executes real application code, enabling you to simulate distributed systems with thousands of network-connected processes in realistic and scalable private network experiments using your laptop, desktop, or server running Linux.
coreutils - upstream mirror