Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: len@rufus.math.nwu.edu (Len Evens)
Newsgroups: comp.sys.sun
Subject: Re: Adding clients under 4.0
Message-ID: <8902191441.AA16888@rufus.math.nwu.edu>
Date: 1 Mar 89 19:23:10 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 30
Approved: Sun-Spots@rice.edu
Original-Date: Sun, 19 Feb 89 08:41:45 CST
X-Sun-Spots-Digest: Volume 7, Issue 176, message 5 of 12

I previously reported a problem with adding a new client under OS 4.0 with
the client's swap file in a directory created in /home.  Thanks to Bill
Gilroy's response, I looked carefully at the documentation for exportfs
and discovered the source of my problem.  The man page explicitly warns
that you can't export a subdirectory in the same file system of something
which was previously exported.   Since I had previously decided to mount
the client's home directory on /home on the server (to avoid duplication
of home directories), /home was being exported,  and since I had created a
swap path named /home/swap, I was attempting to do just that.   If I had
followed the `rules' and put the clients /home directory in /home/client
on the server, there presumably would have been no problem.

I am still a bit perplexed about where if anywhere the client's swapping
was going and why the error messages during booting didn't indicated more
clearly that something was wrong.

I eventually dealt with the problem by repartitioning the disk, but that
is another story.

Leonard Evens                      len@math.nwu.edu
Department of Mathematics 
Northwestern University
Evanston, IL 60208
312-491-5537

[[ That reminds me....one time when we set up a client with
"setup_client", there wasn't enough room in /export/swap for the swap file
we requested.  Of course, "setup_client" didn't say anything and of course
we tried to boot the client.  Ever try to boot a machine with a swap space
of zero size?  Fun.  --wnl ]]