home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!usenet.coe.montana.edu!news.u.washington.edu!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
- From: Sean.Levy@cs.cmu.edu
- Newsgroups: comp.unix.programmer
- Subject: Re: Determining the state of a process on another host
- Message-ID: <Uf_F7eO00hMg9m_mV7@cs.cmu.edu>
- Date: 11 Dec 92 12:10:50 GMT
- Article-I.D.: cs.Uf_F7eO00hMg9m_mV7
- References: <1992Dec10.154438.13881@dd.dk>
- Organization: Carnegie Mellon, Pittsburgh, PA
- Lines: 30
- In-Reply-To: <1992Dec10.154438.13881@dd.dk>
-
- Excerpts from netnews.comp.unix.programmer: 10-Dec-92 Determining the
- state of a .. Mads Westermann@dd.dk (770)
-
- > Is
- there any way of doing a remote kill(...,0) ??
-
- In a word, no. Toolkits like ISIS and DPSK provide this functionality,
- plus a whole lot more, but you can't count on anything like this in a
- generic unix environment (actually, in just about any unix environment I
- know of. Maybe sprite has it, but I'm not sure, as I'm still
- reading/digesting the papers).
-
- If you're running berkeley r* stuff, you could try something cheesy like
- rsh/rexec'ing to the remote host and ps'ing the pid. Gross, but could
- work. See rcmd(3).
-
- Alternatively, and probably more sensibly, you could have an AYT (Are
- You There) message in your client/server protocol. This is the approach
- I've used, and it works well (and doesn't depend on anything else being
- in the environment).
-
- Good luck,
- -- Sean
- --
- Sean Levy, n-dim Group
- Engineering Design Research Center, CMU
-
- US Mail: 5000 Forbes Ave, Pittsburgh, PA 15213
- Email: snl+@cmu.edu (MIME and ATK accepted)
- Phones: +1 412 268 {5217(lab),5221(ans.mach.),5229(fax)}
-