On Thursday 02 February 2006 18:35, Andrew Sackville-West wrote: >On Thu, 02 Feb 2006 18:23:51 -0500 > >Gene Heskett <[EMAIL PROTECTED]> wrote: >> On Thursday 02 February 2006 13:14, Andrew Sackville-West wrote: >> >On Thu, 02 Feb 2006 08:57:43 -0500 >> > >> >Gene Heskett <[EMAIL PROTECTED]> wrote: >> >> On Wednesday 01 February 2006 02:39, Gene Heskett wrote: >> >> >Greetings; >> >> >> >> And no one has any comments to make on this? >> > >> >not a clue. why samba and not nfs? >> >> Because I have yet, despite quite a bit of expert handholding, ever >> been able to make NFS work for anything here. No permissions >> returns is all I can get. Also, even though the NSF starter is >> being run by the bootup, it always logs the message that NFS4-MTAB >> doesn't exist. On the bootup screen but nowhere else in the logs. >> And questions asked about that on the net have now been uniformly >> ignored on the major lists I haunt for about 4 years now. :( > >well, that's wierd. I've only used nfs for a few months now (slowly > trying to convert my house to 'doze free) and had no difficulty from > day one. I've certainly never seen that message before and I have one > machine that boots a couple times a day (mythtv with automatic > booting weeee!). Which side does this show on? server or client?
That would be this machine, the server. The exact message (all the setup stuff is still setup AFAIK) is: [EMAIL PROTECTED] etc]# service nfs restart Shutting down NFS mountd: [FAILED] Shutting down NFS daemon: [FAILED] Shutting down NFS quotas: [FAILED] Shutting down NFS services: [ OK ] Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] Starting NFS4 idmapd: Error: RPC MTAB does not exist. And it will repeat that manta ad infinitum. [EMAIL PROTECTED] etc]# service nfs restart Shutting down NFS mountd: [ OK ] Shutting down NFS daemon: [ OK ] Shutting down NFS quotas: [ OK ] Shutting down NFS services: [ OK ] Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] Starting NFS4 idmapd: Error: RPC MTAB does not exist. A man idmapd make no mention of that file... And in the log, Feb 2 19:48:20 coyote rpc.mountd: Caught signal 15, un-registering and exiting. Feb 2 19:48:20 coyote nfs: rpc.mountd shutdown succeeded Feb 2 19:48:25 coyote kernel: nfsd: last server has exited Feb 2 19:48:25 coyote kernel: nfsd: unexporting all filesystems Feb 2 19:48:25 coyote nfs: nfsd shutdown succeeded Feb 2 19:48:25 coyote nfs: rpc.rquotad shutdown succeeded Feb 2 19:48:25 coyote nfs: Shutting down NFS services: succeeded Feb 2 19:48:25 coyote nfs: Starting NFS services: succeeded Feb 2 19:48:25 coyote nfs: rpc.rquotad startup succeeded Feb 2 19:48:25 coyote nfs: rpc.nfsd startup succeeded Feb 2 19:48:25 coyote nfs: rpc.mountd startup succeeded and any attempt to mount the share from another machine gets a no permission response that never changes. > personally, I like nfs as it "just works" for me here. of course, > this is all internal to my house ona trusted lan with no protections > blah blah blah. > >> >FWIW, I killed fam, and >> > >> >> things seem to be working more or less normally here. Killing fam >> >> allowed me to umount those shares. This is required because I >> >> have a script (cron) that remounts some shares daily else they >> >> get stale or something and quit working, or did back when I set >> >> that script up 5 years ago because it would quit working at odd >> >> times. >> > >> >is this a bug with fam? I've had some trouble umounting nfs shares >> > on occaision for no apparent reason, though umount -l does the >> > trick. >> >> But what happens then if the share is to be immediatelty remounted, >> like my little daily insurance cron script does.? > >don't know, but if its fam that is causing it to be busy, I don't > think its a big deal. but I know less than nothing about fam and how > it works. I can vouch for the fact that fam DOESN'T like to have a share its watching get rebooted, because then you have to reboot the box fam is running on in order to be able to mount that share anew. That it isn't handling its errors at all well, plus I've NDI what starts it when I reboot this box, makes fam less than worthless to me. Yes, IMO it (fam) needs help if its to be helpfull in the long view. Ssh used to be that way too, but it now cleans up after itself rather nicely since a year or so back. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
