Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!lll-winken!aunro!alberta!edson!news
From: eric@dino (Eric Norum,EB 547,4626,)
Newsgroups: comp.sys.next
Subject: Re: rusersd
Message-ID: <1991Jun6.151530.12608@ee.ualberta.ca>
Date: 6 Jun 91 15:15:30 GMT
References: <4T1133w164w@ersys.edmonton.ab.ca>
Sender: news@ee.ualberta.ca
Organization: Univ. of Alberta
Lines: 27
Originator: eric@bode.ee.ualberta.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. Well, I checked the /etc/inetd.conf file, and it has the 
> rusersd and rwhod lines, but these daemons don't seem to be starting on 
> boot. I can run rusers, but have to Ctrl-C out of it instead of getting a 
> clean exit. Can somebody help?
> 
> -drin
> 
> Adrian Smith              drin@ersys.edmonton.ab.ca
> Edmonton Remote Systems:  Serving Northern Alberta since 1982

inetd doesn't start the daemons, it just sits waiting for a connection
on the appropriate port number.  When some other machine does an `rusers'
the inetd detects the connection request and starts up /usr/etc/rpc.rusersd.

Regarding the `no-clean exit', I think you just have to be more patient.
The rusers program doesn't know how many replies to expect, so it just
waits for a while before terminating.  On the NeXT here it times out in
about 2 minutes.
-- 
Eric Norum
Dept. of Electrical Engineering      eric@ee.ualberta.ca
University of Alberta
Edmonton, Canada.                   phone: (403) 492-4626