Nukesor
commented
3 weeks ago Good points, that feature request sounds pretty reasonable.
It's definitely possible to do, however a few things need to be done first.
Specifically #548, otherwise the message handlers won't have access to the process handles.
Once the refactoring has taken place, the next steps are rather straight forward.
- We have to think about a good name for the command. Maybe just a
psor atasksubcommand? - It needs to be decided which process should be shown. My approach would be to show the direct child, which is the shell in most cases. The reason for this is that shells do weird stuff, are platform specific and users can now use custom shell commands, which makes it even harder to get this right. To give a few examples:
sh -c 'echo "test"'actually get's rid of theshparent process so thatecho "test"as a direct subprocess of Pueuesh -c 'echo "test" && echo "another test"doesn't and there's always theshparent.sh -c './some_script.sh'starts a singleshshell as parent process, which then processes some commands from that script.sh -c 'echo "test" && ./some_script.sh'starts ashparent process, which then contains anothershprocess that executes commands from that script.
Some shells start futher subprocesses, some don't. It's basically up to the shell. Process handling in Windows is also completely different than in Linux and even though Mac process handling is similar, nobody is interested in writing a process handling library for it.
Due to these reasons and the sake of maintainability, I would strongly prefer to not do any shell specific shenannigans to determine the first process that's not a shell, as this is very error prone and it's easy to run into race conditions (e.g. looking up a subprocess when the parent just finished and is destroyed). The user can then use the shell's or root process's pid to do further processing as they like.
vvuk
A detailed description of the feature you would like to see added.
This was mentioned in #364 which was closed because the original issue author stopped needing it. I came to
pueuevianushell, where it's a suggested way to work aroundnushell's lack of process management. And for the most part it's great, and far better than bash/zsh process management. However, I frequently just need the process ID of the background process I spawned.I understand this isn't always a simple thing to provide; however, ultimately, there is a process that the pueue daemon launches for a task. That might be a shell if shell execute is used -- which I understand is supposed to be always, but it seems like this is skipped in some instances. When launching an app, I see the app process as a child of the daemon, without a shell in between. But either way, I'd like to easily obtain the process ID of whatever the thing is that the daemon launched, even if it's the shell. (Indeed I just tested -- if I include shell special characters like
>then sh is launched)Explain your usecase of the requested feature
Using pueue as a general rich background task manager. Sometimes the process ID is needed -- attaching a debugger/profiler, for example. It would be very convenient if this was easily available.
Alternatives
ps -ef | grepand then hunt for the process you want. Doable, but not pleasant.Additional context
No response