home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.security:5214 comp.unix.shell:5139
- Newsgroups: alt.security,comp.unix.shell
- Path: sparky!uunet!timbuk.cray.com!walter.cray.com!btk
- From: btk@cray.com (Bryan Koch)
- Subject: Re: rsh (detect?)
- Message-ID: <1992Dec22.163331.3145@walter.cray.com>
- Lines: 20
- Sender: Bryan Koch
- Nntp-Posting-Host: matrix.cray.com
- Organization: Cray Research, Inc.
- References: <1992Dec22.205235.10198@exu.ericsson.se>
- Date: 22 Dec 92 16:33:30 CST
-
- In article <1992Dec22.205235.10198@exu.ericsson.se> lmcstst@noah.ericsson.se (Stamos Stamos) writes:
- >
- >Is there any way to detect other users running programs via 'rsh' on your
- >machine(sun slc)?
- >Other than running 'ps' every few seconds, and greping the output.
-
- We've modified in.rshd to do logging the same way that ftp and login do.
- rsh/rcp information is It is then available via the "last" command.
- A sample:
-
- xxx %xxx mist Tue Dec 22 16:15 - 16:15 (00:00)
- yyy %zzz snoid Tue Dec 22 14:26 - 14:26 (00:00)
-
- The first of shows the use of login "xxx" from remote machine "mist". The
- local and remote user IDs are the same. The second example shows remote
- user "zzz" making use of local login ID "yyy".
-
- If all you want to know about is what people are doing, then process
- accounting via the lastcomm command may suffice. Its unfortunate that
- process accounting isn't enabled by default.
-