Keep shell open but kill a command about libsuperuser HOT 7 CLOSED

There's no way to kill individual commands, as there's no way to send the signal (without opening a secondary shell).

You could have a secondary shell open (the entire time) and send kill commands through that.

Or you could start inotifywait -m & so the inotify process is run async, and you can issue the kill command through the primary shell.

It's just shell coding, be creative.

from libsuperuser.

Thanks for the feedback. I will play around with opening a secondary shell or just use the recursive flag for inotifywait. :)

from libsuperuser.

On Apr 1, 2015 7:59 AM, "Jared Rummler" [email protected] wrote:

Thanks for the feedback. I will play around with opening a secondary
shell or just use the recursive flag for inotifywait. :)

—
Reply to this email directly or view it on GitHub.

from libsuperuser.

Thank you so so much
On Apr 1, 2015 7:59 AM, "Jared Rummler" [email protected] wrote:

Thanks for the feedback. I will play around with opening a secondary
shell or just use the recursive flag for inotifywait. :)

—
Reply to this email directly or view it on GitHub.

from libsuperuser.

Thank yoi
On Apr 1, 2015 7:59 AM, "Jared Rummler" [email protected] wrote:

Thanks for the feedback. I will play around with opening a secondary shell
or just use the recursive flag for inotifywait. :)

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

from libsuperuser.

Okay, so I think killing the command in another shell is the way to go. However, I am trying to find the best way to get the PID for the command.

I am getting the PID of the process using this static factory method I wrote:

public static int getPid(Process process) {
    try {
        Class<?> ProcessImpl = process.getClass();
        Field field = ProcessImpl.getDeclaredField("pid");
        field.setAccessible(true);
        return field.getInt(process);
    } catch (NoSuchFieldException | IllegalAccessException | IllegalArgumentException e) {
        return -1;
    }
}

This returns the PID for the shell and not the command. Example: got 25396 and ran ps | grep 25396:

u0_a153   25396 25366 3188   364   c0275ca8 b6f8bb68 S su

Do you know how I can get the PID of the command? I guess I can parse the output of ps. For example: running the following command gives me the PID I'm looking for:

ps | grep inotifywait

root      25408 25404 3168   820   c0275ca8 b6ea4b68 S /data/data/com.jrummyapps.rootbrowser/files/inotifywait/armeabi-v7a/inotifywait

This approach is not desirable because multiple inotifywait processes could be running.

Do you know of a better approach to getting the PID for the command and not the shell?

from libsuperuser.

Got it working. You can close this.

from libsuperuser.