Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263757
| From | Franco Martelli <martellif67@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Get running time of child process |
| Date | 2023-11-21 16:40 +0100 |
| Message-ID | <HCB0Z-70XD-13@gated-at.bofh.it> (permalink) |
| References | <HCiB3-6NSG-3@gated-at.bofh.it> <HCj45-6Ohz-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 20/11/23 at 21:22, Michael Kjörling wrote:
> $ ps -eo pid,lstart,etime -q 1620,3507
>
> If that doesn't return anything for the child process, maybe it simply
> has exited?
Thanks it works, but instead of the child PID it is shown the parent PID:
~$ ps -eo pid,lstart,etime -q 1620,6841
PID STARTED ELAPSED
1620 Mon Nov 20 16:12:47 2023 23:47:16
1620 Tue Nov 21 15:59:36 2023 00:28
for me it doesn't matter, it is obvious that the last row refers to the
child process. Picom forks a new child when its configuration file is
changed:
~$ touch /home/myuser/.config/picom.conf
now the new Picom's child has PID 6841, thanks again
--
Franco Martelli
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Get running time of child process Franco Martelli <martellif67@gmail.com> - 2023-11-20 21:00 +0100
Re: Get running time of child process Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-11-20 21:30 +0100
Re: Get running time of child process Franco Martelli <martellif67@gmail.com> - 2023-11-21 16:40 +0100
Re: Get running time of child process Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-11-21 17:50 +0100
Re: Get running time of child process Franco Martelli <martellif67@gmail.com> - 2023-11-21 20:50 +0100
Re: Get running time of child process <tomas@tuxteam.de> - 2023-11-22 06:40 +0100
csiph-web