ruptime reports 0 users (it's *

[preece at ccvaxa.UUCP]

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 at gswd-vms