Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-08 Thread Kenneth Wolcott
Thank you, you have provided lots of help which I need to fully digest.. Ken On Sat, Apr 8, 2023 at 5:09 PM Richard L. Hamilton wrote: > > If you're trying to be exact and ONLY get the process you're probably > interested in, here's a scenario: > > sh-3.2$ pgrep -lf CARROT # list process-id and

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-08 Thread Richard L. Hamilton
If you're trying to be exact and ONLY get the process you're probably interested in, here's a scenario: sh-3.2$ pgrep -lf CARROT # list process-id and full command line 911 /Applications/CARROTweather.app/Contents/MacOS/CARROTweather sh-3.2$ pgrep -l CARROT # list process-id and just command nam

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-08 Thread Kenneth Wolcott
Hi Richard; Thank you for your additional input. Apparently I was over-thinking pgrep+pkill in my earlier attempts. I have implemented your suggestions in my script and it appears to work fine. Thanks, Ken Wolcott On Fri, Apr 7, 2023 at 9:27 PM Richard L. Hamilton wrote: > > Not seeing

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-08 Thread Eckard Brauer
if I didn't misunderstand UNIX signals too much, there are a few signals which can't be ignored. That means, after an optional signal handling routine has been run, the deconstruction and remove of the specific process is (or should be) enforced by the OS itself. SIGKILL, SIGSEGV, SIGILL should at

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-07 Thread Richard L. Hamilton
Not seeing that, if this fits your scenario: sh-3.2$ open -a TextEdit sh-3.2$ pgrep -lf TextEdit 68476 /System/Applications/TextEdit.app/Contents/MacOS/TextEdit sh-3.2$ pkill TextEdit # it went away... SIGTERM is (usually) like Quit; SIGKILL is like Force Quit. A process may ignore SIGTERM; the

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-07 Thread Kenneth Wolcott
> inspect it, etc. In addition to owner being the same, some signed or > sandboxed processes may be able to refuse being attached to or traced. > > Don't forget top, Activity Monitor, and (for certain information) lsof. > > > On Apr 7, 2023, at 22:39, Kenneth Wolcott

Re: what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-07 Thread Richard L. Hamilton
processes may be able to refuse being attached to or traced. Don't forget top, Activity Monitor, and (for certain information) lsof. > On Apr 7, 2023, at 22:39, Kenneth Wolcott wrote: > > Hi; > > what port(s) give me good control over processes (list, kill, etc) > better

what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill

2023-04-07 Thread Kenneth Wolcott
Hi; what port(s) give me good control over processes (list, kill, etc) better than MacOS pgrep+pkill? It would be great if MacOS has /proc filesystem like Linux. Thanks, Ken Wolcott