Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site ccvaxa
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!preece
From: preece@ccvaxa.UUCP
Newsgroups: net.bugs.4bsd
Subject: Re: ruptime reports 0 users (it's *
Message-ID: <5700003@ccvaxa>
Date: Mon, 16-Dec-85 10:40:00 EST
Article-I.D.: ccvaxa.5700003
Posted: Mon Dec 16 10:40:00 1985
Date-Received: Wed, 18-Dec-85 02:47:19 EST
References: <11232@ucbvax.BERKELEY.EDU>
Lines: 19
Nf-ID: #R:ucbvax.BERKELEY.EDU:11232:ccvaxa:5700003:000:726
Nf-From: ccvaxa.UUCP!preece    Dec 16 09:40:00 1985


I'd suggest having the rwho message contain a window into the user
list, containing at most n entries per window.  After each sending
the window is advanced in the list, eventually wrapping around to
the beginning.  N is based on the max packet size.  Thus it still sends
the more important stuff (the ruptimme info) at the highest
frequency and just keeps the rwho list a little less current.
This generates less net traffic than sending the whole list,
in multiple packets, at each shot.

I think the rwho list is worth having.  A solution which just
set a flag indicating the list was too long would not be a
reasonable solution.

-- 
scott preece
gould/csd - urbana
uucp:	ihnp4!uiucdcs!ccvaxa!preece
arpa:	preece@gswd-vms