Hi Folks!
I have a different queued job stuck. Tried the instructions given
previous (see Subject of “Queued Job Stuck” ~Aug. 17^th ). The problem
this time is the PID number is incrementing!
barry@BE4:~$ date && ps -ef | grep mythcommflag
Fri 01 Sep 2023 11:44:28 AM CDT
barry 1024881 1024862 0 11:44 pts/0 00:00:00 grep --color=auto mythcommflag
barry@BE4:~$ date && ps -ef | grep mythcommflag
Fri 01 Sep 2023 11:44:28 AM CDT
barry 1024884 1024862 0 11:44 pts/0 00:00:00 grep --color=auto mythcommflag
Got that by repeating the command in less than a second and the PID
incremented by three (sometimes only by two).
So the problem is I can’t enter a PID to kill because what I see is no
longer valid. Noted the PPID is constant – tempting! <g>
There are shows currently recording – is that the reason?
TIA! Barry
I have a different queued job stuck. Tried the instructions given
previous (see Subject of “Queued Job Stuck” ~Aug. 17^th ). The problem
this time is the PID number is incrementing!
barry@BE4:~$ date && ps -ef | grep mythcommflag
Fri 01 Sep 2023 11:44:28 AM CDT
barry 1024881 1024862 0 11:44 pts/0 00:00:00 grep --color=auto mythcommflag
barry@BE4:~$ date && ps -ef | grep mythcommflag
Fri 01 Sep 2023 11:44:28 AM CDT
barry 1024884 1024862 0 11:44 pts/0 00:00:00 grep --color=auto mythcommflag
Got that by repeating the command in less than a second and the PID
incremented by three (sometimes only by two).
So the problem is I can’t enter a PID to kill because what I see is no
longer valid. Noted the PPID is constant – tempting! <g>
There are shows currently recording – is that the reason?
TIA! Barry