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

[Kenneth Wolcott]

Hi Richard;

  Thanks for the info.  I'll look into those.

  I found that a process that I started by using the MacOS open
command could be listed by prep but I could not kill it with pkill
(silently fails, like a no-op).

Thanks,
Ken

On Fri, Apr 7, 2023 at 7:54 PM Richard L. Hamilton <rlhamil at smart.net> wrote:
>
> While AFAIK there is not a /proc port, there are FUSE based procfs implementations for macOS. They are limited in the information they can provide, they're using system calls rather than actually digging into the kernel, so they can only provide what the system calls they use offer. So I don't think you can for example see into a process address space with it.  I had it set up some time ago; not sure what FUSE versions or macOS versions it would work with, and didn't really think it worth the bother to keep it set up.
>
> The procs port claims to be an advanced ps with more information.
>
> pfind (also in proctools along with pgrep and pkill) looks to offer much more powerful selection of processes to list; RTFM.
>
> If permissions allow, lldb should be able to attach to a process, control it, 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 <kennethwolcott at gmail.com> wrote:
> >
> > 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
> >
>