Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 21:50:26 +0400, Boris Samorodov wrote: On Tue, 10 Apr 2007 20:34:31 +0300 Giorgos Keramidas wrote: On 2007-04-10 08:55, David Benfell [EMAIL PROTECTED] wrote: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. Hmmm, something odd is going on. Can you show us the output of the command: % cat -vte /etc/exports And: % df as well. On the server: earth% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 62963306 16456346 4146989628%/ devfs 110 100%/dev /dev/ad0s1d 62963306 208880 57717362 0%/var/db /dev/ad2s1d 76168552 48096588 2197848069%/home /dev/ad3s1d 81221264 7472352 0%/rvm/data /dev/ad3s1e 10129744 931934 0%/rvm/log /dev/ad3s1f 266573564 24524764 0%/vicepa /dev/ad2s1e 75200072 2518722 5346 4%/public /dev/ad0s1e 63274730 6595650 5161710211%/reserve linprocfs 440 100%/usr/compat/linux/proc (sfs) 000 100%/sfs (sfswait) 000 100%. /dev/cd0 143168 1431680 100%/cdrom On the client: lupin% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 507630 3981166890485%/ devfs110 100%/dev /dev/ad0s1e 507630 284 466736 0%/tmp /dev/ad0s1f 31283108 7822324 2095813627%/usr /dev/ad0s1d252516674342 2248812 3%/var 192.168.19.243:/home 76168552 48096604 2197846469%/home linprocfs440 100% /usr/compat/linux/proc I considered the possibility that /usr/compat/linux/proc might be a problem *on the client*, but umounting it there made no difference. I'm assuming it can't make any difference on the server side, and I had previously tried a more specific directory--/usr/ports--with the same result. What I would realoly like to do is share /usr/src--if that won't screw up a buildworld--and /usr/ports/distfiles; I'm assuming sharing more could create problems. Thanks! WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgporXjTjnDCW.pgp Description: PGP signature
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 23:11:32 -0700 David Benfell wrote: On Tue, 10 Apr 2007 21:50:26 +0400, Boris Samorodov wrote: On Tue, 10 Apr 2007 20:34:31 +0300 Giorgos Keramidas wrote: On 2007-04-10 08:55, David Benfell [EMAIL PROTECTED] wrote: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 ^^ [1] #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 ^^ [1] /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. Hmmm, something odd is going on. Can you show us the output of the command: % cat -vte /etc/exports And: % df as well. On the server: earth% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 62963306 16456346 4146989628%/ So, / and /usr are parts of one slice. That's the problem [1]. One can have only one line per slice at /etc/exports. devfs 110 100%/dev /dev/ad0s1d 62963306 208880 57717362 0%/var/db /dev/ad2s1d 76168552 48096588 2197848069%/home /dev/ad3s1d 81221264 7472352 0%/rvm/data /dev/ad3s1e 10129744 931934 0%/rvm/log /dev/ad3s1f 266573564 24524764 0%/vicepa /dev/ad2s1e 75200072 2518722 5346 4%/public /dev/ad0s1e 63274730 6595650 5161710211%/reserve linprocfs 440 100%/usr/compat/linux/proc (sfs) 000 100%/sfs (sfswait) 000 100%. /dev/cd0 143168 1431680 100%/cdrom On the client: lupin% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 507630 3981166890485%/ devfs110 100%/dev /dev/ad0s1e 507630 284 466736 0%/tmp /dev/ad0s1f 31283108 7822324 2095813627%/usr /dev/ad0s1d252516674342 2248812 3%/var 192.168.19.243:/home 76168552 48096604 2197846469%/home linprocfs440 100% /usr/compat/linux/proc I considered the possibility that /usr/compat/linux/proc might be a problem *on the client*, but umounting it there made no difference. I'm assuming it can't make any difference on the server side, and I had previously tried a more specific directory--/usr/ports--with the same result. What I would realoly like to do is share /usr/src--if that won't screw up a buildworld--and /usr/ports/distfiles; I'm assuming sharing more could create problems. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Wed, 11 Apr 2007 11:30:37 +0400 Boris Samorodov wrote: earth% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 62963306 16456346 4146989628%/ So, / and /usr are parts of one slice. That's the problem [1]. One can have only one line per slice at /etc/exports. Sorry, not per slice but per filesystem. I.e. you should use one line per directories located at /dev/ad0s1a, etc. devfs 110 100%/dev /dev/ad0s1d 62963306 208880 57717362 0%/var/db /dev/ad2s1d 76168552 48096588 2197848069%/home /dev/ad3s1d 81221264 7472352 0%/rvm/data /dev/ad3s1e 10129744 931934 0%/rvm/log /dev/ad3s1f 266573564 24524764 0%/vicepa /dev/ad2s1e 75200072 2518722 5346 4%/public /dev/ad0s1e 63274730 6595650 5161710211%/reserve linprocfs 440 100%/usr/compat/linux/proc (sfs) 000 100%/sfs (sfswait) 000 100%. /dev/cd0 143168 1431680 100%/cdrom WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Wed, 11 Apr 2007 12:04:15 +0400, Boris Samorodov wrote: On Wed, 11 Apr 2007 11:30:37 +0400 Boris Samorodov wrote: earth% df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 62963306 16456346 4146989628%/ So, / and /usr are parts of one slice. That's the problem [1]. One can have only one line per slice at /etc/exports. Sorry, not per slice but per filesystem. I.e. you should use one line per directories located at /dev/ad0s1a, etc. Okay, success! Thanks! It took several tries to get it quite right, with several reboots of *both* systems; I guess there's some handshaking that is tenuous rather than robust. The most recent version is: / -alldirs -maproot=root 127.0.0.1 192.168.19.1 66.93.170.243 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 #/usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 I had to add 66.93.170.243, the external address of the system, because when I made the other change, I saw complaints from sfs stuff that I'd never gotten working. It is just possible we've now killed two birds with one stone. Thanks! -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgpxiaYsco6go.pgp Description: PGP signature
Re: What am I not understanding about /etc/exports?
On 2007-04-06 20:57, David Benfell [EMAIL PROTECTED] wrote: On Sat, 07 Apr 2007 01:56:41 +0300, Giorgos Keramidas wrote: To allow NFS mounts to work correctly from hosts in the IP ranges 192.168.18.XXX, 192.168.19.XXX listed in your /etc/exports file, you will have to extend the list of addressed permitted for 'rpcbind'. I'd definitely missed that. Unfortunately, correcting it (both on client and server) seems to have made no difference. I still have the same symptoms, as if I need to send a HUP signal someplace (but if this is true, then where?). AFAIR, you have to restart at leats the following: /etc/rc.d/rpcbind restart /etc/rc.d/mountd restart ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 15:24:26 +0300, Giorgos Keramidas wrote: On 2007-04-06 20:57, David Benfell [EMAIL PROTECTED] wrote: On Sat, 07 Apr 2007 01:56:41 +0300, Giorgos Keramidas wrote: To allow NFS mounts to work correctly from hosts in the IP ranges 192.168.18.XXX, 192.168.19.XXX listed in your /etc/exports file, you will have to extend the list of addressed permitted for 'rpcbind'. I'd definitely missed that. Unfortunately, correcting it (both on client and server) seems to have made no difference. I still have the same symptoms, as if I need to send a HUP signal someplace (but if this is true, then where?). AFAIR, you have to restart at leats the following: /etc/rc.d/rpcbind restart /etc/rc.d/mountd restart Progress! Or at least something different, now... Now it says, on the client, RPC: Program not registered. A google search yielded the suggestion that I should reboot the client; this made no difference. Stranger still, and different from the scenario described in the page, there are no messages about NFS in /var/log/messages on the server; it notes that the slave went down (when I rebooted the client) and came back up, okay. On the client, I'm seeing messages from NIS indicating that it couldn't get a UDP handle to ypxfer. Whoops. I checked the packet filtering instructions on both systems; these seem okay. So I tried rebooting the server, and now I'm right back where I started. But I noticed a complaint that it couldn't change the attributes on /usr: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgpcaWjVBZKUh.pgp Description: PGP signature
Re: What am I not understanding about /etc/exports?
On 2007-04-10 12:03, Jason Moss [EMAIL PROTECTED] wrote: Can you please take me off of your mailing list. Thanks! Not really. If you really want to unsubscribe from the freebsd-questions mailing list, only _you_ can do this for your own email address. There is a nice web interface online, at: http://lists.freebsd.org/mailman/listinfo/freebsd-questions which you can use to subscribe, unsubscribe, edit your subscription options, etc. Feel free to use it :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
Can you please take me off of your mailing list. Thanks! On 4/10/07, David Benfell [EMAIL PROTECTED] wrote: On Tue, 10 Apr 2007 15:24:26 +0300, Giorgos Keramidas wrote: On 2007-04-06 20:57, David Benfell [EMAIL PROTECTED] wrote: On Sat, 07 Apr 2007 01:56:41 +0300, Giorgos Keramidas wrote: To allow NFS mounts to work correctly from hosts in the IP ranges 192.168.18.XXX, 192.168.19.XXX listed in your /etc/exports file, you will have to extend the list of addressed permitted for 'rpcbind'. I'd definitely missed that. Unfortunately, correcting it (both on client and server) seems to have made no difference. I still have the same symptoms, as if I need to send a HUP signal someplace (but if this is true, then where?). AFAIR, you have to restart at leats the following: /etc/rc.d/rpcbind restart /etc/rc.d/mountd restart Progress! Or at least something different, now... Now it says, on the client, RPC: Program not registered. A google search yielded the suggestion that I should reboot the client; this made no difference. Stranger still, and different from the scenario described in the page, there are no messages about NFS in /var/log/messages on the server; it notes that the slave went down (when I rebooted the client) and came back up, okay. On the client, I'm seeing messages from NIS indicating that it couldn't get a UDP handle to ypxfer. Whoops. I checked the packet filtering instructions on both systems; these seem okay. So I tried rebooting the server, and now I'm right back where I started. But I noticed a complaint that it couldn't change the attributes on /usr: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). -- jason moss vergo | design 215.805.8010 [EMAIL PROTECTED] www.vergodesign.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On 2007-04-10 08:55, David Benfell [EMAIL PROTECTED] wrote: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. Hmmm, something odd is going on. Can you show us the output of the command: % cat -vte /etc/exports ?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 12:03:47 -0400 Jason Moss [EMAIL PROTECTED] wrote: Can you please take me off of your mailing list. It appears that we are having an epidemic of Googlers who lack the ability to remove themselves from the mail list. Have you ever actually read all the way to the bottom of a posting? There are directions prominently posted there. OK, just follow these directions: freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] So easy a Googler could do it (hopefully)! -- Gerard I don't deserve this award, but I have arthritis and I don't deserve that either. Jack Benny signature.asc Description: PGP signature
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 20:34:31 +0300 Giorgos Keramidas wrote: On 2007-04-10 08:55, David Benfell [EMAIL PROTECTED] wrote: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. Hmmm, something odd is going on. Can you show us the output of the command: % cat -vte /etc/exports And: % df as well. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 13:47:29 -0400 Jason Moss [EMAIL PROTECTED] wrote: Gerard, I have unsubscribed three times and this is what I've been receiving in return: The results of your email command are provided below. Attached is your original message. - Results: [EMAIL PROTECTED] is not a member of the freebsd-questions mailing list - Unprocessed: unsubscribe unsubscribe - Done. I received this three times but still getting tons of emails. I also did it from the website! You must be using an incorrect email address to un-subscribe yourself. Send me via forward as attachment a copy of an email from the 'freebsd' list, or if that is not possible, and I don't believe it is easily done via the GMail web interface, a complete copy of the headers from same such email. -- Gerard Silly is a state of Mind, Stupid is a way of Life. signature.asc Description: PGP signature
Re: What am I not understanding about /etc/exports?
On Tue, 10 Apr 2007 20:34:31 +0300, Giorgos Keramidas wrote: On 2007-04-10 08:55, David Benfell [EMAIL PROTECTED] wrote: Apr 10 08:28:59 earth mountd[739]: can't change attributes for /usr Apr 10 08:28:59 earth mountd[739]: bad exports list line /usr -alldirs -maproot Apr 10 08:28:59 earth mountd[739]: network/host conflict I've been here before; the FAQ says, The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS. Which leads me back to the original question. Here's the file: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 And: lupin% showmount -e earth.cybernude.org Exports list on earth.cybernude.org: /public127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 / 127.0.0.1 lupin% As you can see, there are serious discrepancies, here. And I cannot see where my syntax is correct on the lines in /etc/exports that work and incorrect on the lines which don't work. Hmmm, something odd is going on. Can you show us the output of the command: % cat -vte /etc/exports earth% cat -vte /etc/exports / -alldirs -maproot=root 127.0.0.1$ #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1$ /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1$ /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1$ /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1$ /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0$ I think this is what I expect (based on the man page for cat(1)). Thanks! -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgp8yJu3n5Upk.pgp Description: PGP signature
What am I not understanding about /etc/exports?
Hello all, My /etc/exports contains: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 Yet: mountd[735]: mount request denied from 192.168.19.1 for /usr/ports/distfiles And more recently, lupin% sudo showmount -e earth.cybernude.org RPC: Port mapper failure showmount: can't do exports rpc What's going on? Thanks! -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgp4dzIb3GZPM.pgp Description: PGP signature
Re: What am I not understanding about /etc/exports?
On 2007-04-06 11:36, David Benfell [EMAIL PROTECTED] wrote: Hello all, My /etc/exports contains: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 Yet: mountd[735]: mount request denied from 192.168.19.1 for /usr/ports/distfiles And more recently, lupin% sudo showmount -e earth.cybernude.org RPC: Port mapper failure showmount: can't do exports rpc What's going on? Thanks! Do you have /etc/hosts.allow and /etc/hosts.deny files? If yes, what do they contain? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Fri, 06 Apr 2007 22:08:50 +0300, Giorgos Keramidas wrote: On 2007-04-06 11:36, David Benfell [EMAIL PROTECTED] wrote: Hello all, My /etc/exports contains: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 Yet: mountd[735]: mount request denied from 192.168.19.1 for /usr/ports/distfiles And more recently, lupin% sudo showmount -e earth.cybernude.org RPC: Port mapper failure showmount: can't do exports rpc What's going on? Thanks! Do you have /etc/hosts.allow and /etc/hosts.deny files? I don't actually implement these, so they should essentially be from the default install. I do not have /etc/hosts.deny on either the server or the client. The first attachment is /etc/hosts.allow from the server. The second attachment is /etc/hosts.allow from the client. (Both systems are FreeBSD 6.2 stable, within a little over a week or so.) Thanks! -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). # # hosts.allow access control file for tcp wrapped applications. # $FreeBSD: src/etc/hosts.allow,v 1.19.8.1 2006/02/19 14:57:01 ume Exp $ # # NOTE: The hosts.deny file is deprecated. # Place both 'allow' and 'deny' rules in the hosts.allow file. # See hosts_options(5) for the format of this file. # hosts_access(5) no longer fully applies. #_ _ _ # | | __ __ __ _ _ __ ____ __ | | ___ | | # | _| \ \/ / / _` | | '_ ` _ \ | '_ \ | | / _ \ | | # | |___ | (_| | | | | | | | | |_) | | | | __/ |_| # |_| /_/\_\ \__,_| |_| |_| |_| | .__/ |_| \___| (_) # |_| # !!! This is an example! You will need to modify it for your specific # !!! requirements! # Start by allowing everything (this prevents the rest of the file # from working, so remove it when you need protection). # The rules here work on a First match wins basis. ALL : ALL : allow # Wrapping sshd(8) is not normally a good idea, but if you # need to do it, here's how #sshd : .evil.cracker.example.com : deny # Protect against simple DNS spoofing attacks by checking that the # forward and reverse records for the remote host match. If a mismatch # occurs, access is denied, and any positive ident response within # 20 seconds is logged. No protection is afforded against DNS poisoning, # IP spoofing or more complicated attacks. Hosts with no reverse DNS # pass this rule. ALL : PARANOID : RFC931 20 : deny # Allow anything from localhost. Note that an IP address (not a host # name) *MUST* be specified for rpcbind(8). ALL : localhost 127.0.0.1 : allow # Comment out next line if you build libwrap with NO_INET6=yes. ALL : [::1] : allow ALL : my.machine.example.com 192.0.2.35 : allow # To use IPv6 addresses you must enclose them in []'s ALL : [fe80::%fxp0]/10 : allow ALL : [fe80::]/10 : deny ALL : [2001:db8:2:1:2:3:4:3fe1] : deny ALL : [2001:db8:2:1::]/64 : allow # Sendmail can help protect you against spammers and relay-rapers sendmail : localhost : allow sendmail : .nice.guy.example.com : allow sendmail : .evil.cracker.example.com : deny sendmail : ALL : allow # Exim is an alternative to sendmail, available in the ports tree exim : localhost : allow exim : .nice.guy.example.com : allow exim : .evil.cracker.example.com : deny exim : ALL : allow # Rpcbind is used for all RPC services; protect your NFS! # (IP addresses rather than hostnames *MUST* be used here) rpcbind : 192.0.2.32/255.255.255.224 : allow rpcbind : 192.0.2.96/255.255.255.224 : allow rpcbind : ALL : deny # NIS master server. Only local nets should have access ypserv : localhost : allow ypserv : .unsafe.my.net.example.com : deny ypserv : .my.net.example.com : allow ypserv : ALL : deny # Provide a small amount of protection for ftpd ftpd : localhost : allow ftpd : .nice.guy.example.com : allow ftpd : .evil.cracker.example.com : deny ftpd : ALL : allow # You need to be clever with finger; do _not_ backfinger!! You can easily # start a finger war. fingerd : ALL \ : spawn (echo Finger. | \ /usr/bin/mail -s tcpd\: [EMAIL PROTECTED] fingered me! root) \ : deny # The rest of the daemons are protected. ALL : ALL \ : severity auth.info \ : twist /bin/echo You are not welcome to use %d from %h. # # hosts.allow access control file for tcp wrapped applications. # $FreeBSD: src/etc/hosts.allow,v 1.19.8.1 2006/02/19 14:57:01 ume Exp $ # # NOTE: The hosts.deny file is deprecated. # Place both 'allow' and 'deny' rules in the
Re: What am I not understanding about /etc/exports?
On 2007-04-06 15:26, David Benfell [EMAIL PROTECTED] wrote: On Fri, 06 Apr 2007 22:08:50 +0300, Giorgos Keramidas wrote: On 2007-04-06 11:36, David Benfell [EMAIL PROTECTED] wrote: Hello all, My /etc/exports contains: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 Yet: mountd[735]: mount request denied from 192.168.19.1 for /usr/ports/distfiles Do you have /etc/hosts.allow and /etc/hosts.deny files? I don't actually implement these, so they should essentially be from the default install. I do not have /etc/hosts.deny on either the server or the client. The first attachment is /etc/hosts.allow from the server. The server's `hosts.allow' file needs a bit of configuration: # hosts.allow access control file for tcp wrapped applications. # $FreeBSD: src/etc/hosts.allow,v 1.19.8.1 2006/02/19 14:57:01 ume Exp $ [...] # Allow anything from localhost. Note that an IP address (not a host # name) *MUST* be specified for rpcbind(8). ALL : localhost 127.0.0.1 : allow The 127.0.0.1 address above allows rpcbind (and other RPC-based services) to work for localhost - localhost connections. # Rpcbind is used for all RPC services; protect your NFS! # (IP addresses rather than hostnames *MUST* be used here) rpcbind : 192.0.2.32/255.255.255.224 : allow rpcbind : 192.0.2.96/255.255.255.224 : allow rpcbind : ALL : deny These rules allow rpcbind to work for hosts in the IP ranges matching the first two lines. To allow NFS mounts to work correctly from hosts in the IP ranges 192.168.18.XXX, 192.168.19.XXX listed in your /etc/exports file, you will have to extend the list of addressed permitted for 'rpcbind'. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What am I not understanding about /etc/exports?
On Sat, 07 Apr 2007 01:56:41 +0300, Giorgos Keramidas wrote: On 2007-04-06 15:26, David Benfell [EMAIL PROTECTED] wrote: On Fri, 06 Apr 2007 22:08:50 +0300, Giorgos Keramidas wrote: On 2007-04-06 11:36, David Benfell [EMAIL PROTECTED] wrote: Hello all, My /etc/exports contains: / -alldirs -maproot=root 127.0.0.1 #/usr/src -alldirs -maproot=root 127.0.0.1 192.168.19.1 /usr -alldirs -maproot=root 127.0.0.1 192.168.19.1 /public -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /home -alldirs -maproot=root 127.0.0.1 192.168.18.45 192.168.18.46 192.168.19.1 /cdrom -alldirs,quiet,ro 127.0.0.1 -network 192.168 -mask 255.255.0.0 Yet: mountd[735]: mount request denied from 192.168.19.1 for /usr/ports/distfiles Do you have /etc/hosts.allow and /etc/hosts.deny files? I don't actually implement these, so they should essentially be from the default install. I do not have /etc/hosts.deny on either the server or the client. The first attachment is /etc/hosts.allow from the server. The server's `hosts.allow' file needs a bit of configuration: # hosts.allow access control file for tcp wrapped applications. # $FreeBSD: src/etc/hosts.allow,v 1.19.8.1 2006/02/19 14:57:01 ume Exp $ [...] # Allow anything from localhost. Note that an IP address (not a host # name) *MUST* be specified for rpcbind(8). ALL : localhost 127.0.0.1 : allow The 127.0.0.1 address above allows rpcbind (and other RPC-based services) to work for localhost - localhost connections. # Rpcbind is used for all RPC services; protect your NFS! # (IP addresses rather than hostnames *MUST* be used here) rpcbind : 192.0.2.32/255.255.255.224 : allow rpcbind : 192.0.2.96/255.255.255.224 : allow rpcbind : ALL : deny These rules allow rpcbind to work for hosts in the IP ranges matching the first two lines. To allow NFS mounts to work correctly from hosts in the IP ranges 192.168.18.XXX, 192.168.19.XXX listed in your /etc/exports file, you will have to extend the list of addressed permitted for 'rpcbind'. I'd definitely missed that. Unfortunately, correcting it (both on client and server) seems to have made no difference. I still have the same symptoms, as if I need to send a HUP signal someplace (but if this is true, then where?). Thanks! -- David Benfell, LCP [EMAIL PROTECTED] --- Resume available at http://www.parts-unknown.org/ NOTE: I sign all messages with GnuPG (0DD1D1E3). pgpaKv227wTnH.pgp Description: PGP signature
