From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Killing another user's process
Date: Tue, 25 Jul 2017 10:14:37 +0100 [thread overview]
Message-ID: <CAOw7k5i0t3kOKrxU9yc2_JgywCLHUBbZ2s31n0++X3HnEpjfFw@mail.gmail.com> (raw)
In-Reply-To: <CAK9Gx1eVNzxk0RPpVNDTiL48VTcFXOu60ffPUniQ1u177ZDr6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
lower case kill restricts the list to processes of the invoking user
initial cap Kill doesn't do that.
for lower case kill, you can @{rfork n; echo -n none >/tmp/none && bind
/tmp/none /dev/user && kill tftpd}
you wouldn't normally of course but aspects of that command might be
instructive
On 25 July 2017 at 08:34, Peter Hull <peterhull90@gmail.com> wrote:
> Thanks, Skip.
> I thought that ought to work, however 'kill tftpd' doesn't give any
> output. (I can kill other processes)
> I think maybe I have misunderstood the host owner part. If I do a
> plain install (of 9front, actually) from the CD and log in as glenda,
> am I not the host owner?
> Thanks,
> Pete
>
>
> On Mon, 24 Jul 2017 at 20:02 Skip Tavakkolian
> <skip.tavakkolian@gmail.com> wrote:
> >
> > If you're the host owner, you can:
> >
> > Kill tftpd | rc
> >
> > (See rc scripts kill and Kill)
> >
> >
> > On Mon, Jul 24, 2017, 9:41 AM Peter Hull <peterhull90@gmail.com> wrote:
> >>
> >> Is it possible to kill another user's process in plan9?
> >> Specifically I've been messing about with tftpd, which sets itself up
> >> as user 'none' - if I want to stop the tftp server, how do I do that?
> >> Thanks,
> >> Pete
> >>
>
>
[-- Attachment #2: Type: text/html, Size: 1891 bytes --]
next prev parent reply other threads:[~2017-07-25 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 16:40 Peter Hull
2017-07-24 18:23 ` Skip Tavakkolian
2017-07-25 7:34 ` Peter Hull
2017-07-25 9:14 ` Charles Forsyth [this message]
2017-07-25 9:31 ` Peter Hull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOw7k5i0t3kOKrxU9yc2_JgywCLHUBbZ2s31n0++X3HnEpjfFw@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).