<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Not seeing that, if this fits your scenario:<div class=""><br class=""></div><div class="">sh-3.2$ open -a TextEdit<div class="">sh-3.2$ pgrep -lf TextEdit</div><div class="">68476 /System/Applications/TextEdit.app/Contents/MacOS/TextEdit</div><div class="">sh-3.2$ pkill TextEdit</div><div class=""># it went away...</div><div class=""><br class=""></div><div class="">SIGTERM is (usually) like Quit; SIGKILL is like Force Quit.</div><div class=""><br class=""></div><div class="">A process may ignore SIGTERM; the signalling process will not be informed of that. SIGKILL cannot be ignored; although in some Unix implementations, a hang on what's supposed to be fast I/O (like a physical disk, or an NFS mount that's "hard" but not "intr") can make a process unkillable, at least until the hang resolves, if it does; if not, nothing but a reboot will kill such a process. Some implementations block SIGKILL on process 1, because process 1 is essential and there's no good reason to do that.</div><div class=""><br class=""></div><div class="">Sometimes the executable in an app bundle does not have the same name as the app; but a pgrep -lf could match based on the full path includng the app name.</div><div class=""><br class=""></div><div class="">pgrep or pkill not finding something is not an error, although they'll have a return code of one.</div><div class=""><div class="">sh-3.2$ pgrep -lf nosuch</div><div class="">sh-3.2$ echo $?</div><div class="">1</div><div class="">sh-3.2$ pkill nosuch</div><div class="">sh-3.2$ echo $?</div><div class="">1</div></div><div class=""><br class=""></div><div class="">You cannot kill something unless you're root or the same real or effective userid as it is; there MIGHT be other restrictions, Apple liking to be tricky about security. But if it exists and you're not allowed to kill it, that would get an error message:</div><div class=""><div class=""><br class=""></div><div class="">sh-3.2$ pkill syslogd</div><div class="">pkill: signalling pid 161: Operation not permitted</div></div><div class=""><br class=""></div><div class="">Other than those cases, I don't have further guesses what's happening.</div><div class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Apr 7, 2023, at 23:55, Kenneth Wolcott <<a href="mailto:kennethwolcott@gmail.com" class="">kennethwolcott@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Richard;<br class=""><br class=""> Thanks for the info. I'll look into those.<br class=""><br class=""> I found that a process that I started by using the MacOS open<br class="">command could be listed by prep but I could not kill it with pkill<br class="">(silently fails, like a no-op).<br class=""><br class=""></div></div></blockquote><font color="#5856d6" class=""><span style="caret-color: rgb(88, 86, 214);" class="">sh-3.2$ </span></font></div><br class=""></div></body></html>