Xref: utzoo comp.protocols.tcp-ip:7983 comp.protocols.nfs:324
Path: utzoo!yunexus!sparkles!beame
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.nfs
Subject: Re: How to get an urgent message to an arbitrary system
Keywords: rwall
Message-ID: <1989Aug10.170537.1823@maccs.dcss.mcmaster.ca>
Date: 10 Aug 89 17:05:37 GMT
Article-I.D.: maccs.1989Aug10.170537.1823
References: <681@east.East.Sun.COM>
Reply-To: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Organization: McMaster University, Hamilton, Ontario
Lines: 22

In article <681@east.East.Sun.COM> geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>One of the questions I am often asked about PC-NFS is "how come
>there's no way for me to find out when a particular file server
>is going down? Unix users get notified." I point out that (at least
>on SunOS) the mechanism used is "rwall", which is an RPC service, and that
>for size reasons we can't afford to embed a version of rpc.rwalld in 
>PC-NFS. This explanation is reasonable, but unsatisfactory. 
>
>
>Comments?
>

Since we implemented a rwalld in our BWNFS (PC based NFS client), I checked
to see how much memory it takes. Not counting the initialization code, (which
is not resident in memory), it takes 192 (decimal) bytes. 
But I guess if you write in C it takes a lot more :-)

- Carl Beame
  Beame@McMaster.CA

P.S: Geoff, does the new PC-NFS come with a fixed version of rpc.lockd for
     Sun OS4.0.1  ?