Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!stanford.edu!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: rusersd
Message-ID: <1673@toaster.SFSU.EDU>
Date: 7 Jun 91 00:24:39 GMT
References: <4T1133w164w@ersys.edmonton.ab.ca>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 53

In article <4T1133w164w@ersys.edmonton.ab.ca>
	drin@ersys.edmonton.ab.ca (Adrian Smith) writes:
>I've been trying to get rusers running on our local net without much 
>success (all NeXT machines). According to the man pages, inetd should 
>start the rusersd and rwhod daemons and then rusers should work
>correctly.

First of all, rusersd (for rusers, rup) and rwhod (for rwho,
ruptime) are completely separate.

For the former, network activity occurs only when a user issues a
query.  It provides more (and often more accurate) information
about what individual users are doing.  rpc.rusersd is started by
inetd.

For the latter, each machine broadcasts its status at periodic
intervals.  All machines running rwhod update their local caches
on receipt.  It provides a better handle on how machines are
faring.  rwhod is independent of inetd.

Both have advantages, both have tradeoffs.

rusersd:
	The version NeXT ships with 2.0/2.1 is DEFECTIVE.
	You can safely replace it with the 1.0/1.0a version.

	rpc.rusersd is started from inetd; you don't have to
	do anything special to enable it.

rwhod:
	This is shipped DISABLED.  You probably don't want to
	enable it on NetBoot clients (and it's pointless on
	standalone machines).

	1) Create the rwho spool directory:

	mkdir /usr/spool/rwho
	chown agent.daemon /usr/spool/rwho
	chmod 775 /usr/spool/rwho

	2) Add the following to /etc/rc.local in the "Run your
	   own commands here" section:

	if [ -f /usr/etc/rwhod -a -d /usr/spool/rwho ]; then
		/usr/etc/rwhod && (echo -n ' rwhod')		>/dev/console
	fi

	3) Start a copy running:

	cd /
	/usr/etc/rwhod

					-=EPS=-