Re: Can options NFSD and NFSSERVER exist in the same kernel
On Wed, Jul 06, 2011 at 09:33:21PM -0400, Rick Macklem wrote: > Although deleting /etc/rc.d/nfsserver is probably all you need > to do if you have head/etc/rc.d/nfsd, I've attached an updated > nfsd script that I am waiting for a review of. > > If you'd like to test this (when /etc/rc.d/nfsserver is deleted), > it would be appreciated. > > I think it will work for your case, rick I can test this tomorrow. Thanks again for the quick response. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel?
On Wed, Jul 06, 2011 at 08:57:53PM -0400, Rick Macklem wrote: > Steve Kargl wrote: > > So, I upgraded a system from Feb 10 -current to today's > > -current code. In doing so, I changed the kernel config > > options from > > > > options NFSCLIENT # Network Filesystem Client > > options NFSSERVER # Network Filesystem Server > > > > to > > > > options NFSCL # Network Filesystem Client > > options NFSD # Network Filesystem Server > > > > rebuild and install the kernel. Upon rebooting, I'm greeted > > with a > > > > Jul 6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > > kernel module nfsserver > > > > Of course, it can't load nfsserver because I don't use modules > > nor build them. So, why is the system trying to load a nfsserver > > module? Because, my /etc/rc.conf contains > > > > nfs_client_enable="YES" > > nfs_server_enable="YES" > > > > if I change this to > > > > nfs_client_enable="YES" > > nfsv4_server_enable="YES" > > > > The system no longer tries to load nfsserver upon rebooting. > > Unfortunately, this has the effect that no nfsd daemons are > > started. Well, I can start the daemons post-booting. > > > > node16:root[139] /etc/rc.d/nfsd start > > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or > > use 'onestart' instead of 'start'. > > > Assuming you've upgraded your /etc/rc.d scripts to those in head, then > try deleting /etc/rc.d/nfsserver. (This script just tries to load the > old server even though you don't need it unless you want to run the old > one.) > > Or you can build a kernel with both > options NFSD > options NFSSERVER > to make it happy. Thanks for the quick response. I was not sure if these could co-exist in a kernel. Good know that they can. I found that if I include both nfs_server_enable="YES" nfsv4_server_enable="YES" I everything (obviously) works as expected. Perhaps, updating the UPDATING entry that notes that OPTIONS NFSD is now in generic is enough. > I'll try posting to rc@ to see if I can get rid of /etc/rc.d/nfsserver. > > Thanks for pointing this out. I had forgotten about deleting this (and > was until recently confused about when obsolete files get deleted). > > If you still have problems after deleting /etc/rc.d/nfsserver (assuming > your /etc/rc.d scripts are up-to-date), please let me know. I'll try deleting nfsserver tomorrow morning. PS: My intentions are to run your new server (and client) on my cluster to see if I can break them. Why else run -current? :-) -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel
Although deleting /etc/rc.d/nfsserver is probably all you need to do if you have head/etc/rc.d/nfsd, I've attached an updated nfsd script that I am waiting for a review of. If you'd like to test this (when /etc/rc.d/nfsserver is deleted), it would be appreciated. I think it will work for your case, rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel?
Steve Kargl wrote: > On Wed, Jul 06, 2011 at 05:02:37PM -0700, Garrett Cooper wrote: > > On Wed, Jul 6, 2011 at 4:57 PM, Steve Kargl > > wrote: > > > So, I upgraded a system from Feb 10 -current to today's > > > -current code. ?In doing so, I changed the kernel config > > > options from > > > > > > options ? ? ? ? NFSCLIENT ? ? ? ? ? ? ? # Network Filesystem > > > Client > > > options ? ? ? ? NFSSERVER ? ? ? ? ? ? ? # Network Filesystem > > > Server > > > > > > to > > > > > > options ? ? ? ? NFSCL ? ? ? ? ? ? ? ?# Network Filesystem Client > > > options ? ? ? ? NFSD ? ? ? ? ? ? ? ? # Network Filesystem Server > > > > > > rebuild and install the kernel. ?Upon rebooting, I'm greeted > > > with a > > > > > > Jul ?6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > > > kernel module nfsserver > > > > > > Of course, it can't load nfsserver because I don't use modules > > > nor build them. ?So, why is the system trying to load a nfsserver > > > module? ?Because, my /etc/rc.conf contains > > > > > > nfs_client_enable="YES" > > > nfs_server_enable="YES" > > > > > > if I change this to > > > > > > nfs_client_enable="YES" > > > nfsv4_server_enable="YES" > > > > > > The system no longer tries to load nfsserver upon rebooting. > > > Unfortunately, this has the effect that no nfsd daemons are > > > started. ?Well, I can start the daemons post-booting. > > > > > > node16:root[139] /etc/rc.d/nfsd start > > > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf > > > or use 'onestart' instead of 'start'. > > > > Try nfsserver instead of nfsd. Here's the archived discussion of > > my foray into this territory a few months ago: > > http://www.mailinglistarchive.com/html/freebsd-current@freebsd.org/2011-05/msg8.html > > . > > Thanks for the pointer. > > Note, the 20110427 src/UPDATING entry indicates the NFSSERVER has > been changed to NFSD in GENERIC. It seems that one needs to have > both nfs_server_enable and nfsv4_server_enable set to "YES" in > rc.conf to get nfsd daemons started. This is POLA violation for > anyone upgrading from pre-20110427 -current and carrying over > their old /etc/rc.conf. > With -current /etc/rc.d/nfsd and /etc/rc.d/mountd, you shouldn't need to set nfsv4_server_enable="YES". The latter is only needed if you want to support NFSv4. I agree that /etc/rc.d/nfsserver will still try to load the old nfs server if it isn't built into the kernel and I'll look at getting rid of it. I was also trying to minimize the churn in head in case it was necessary to revert the change in default. I'm not sure that an upgrade that doesn't include building and installing new modules can be expected to work correctly when taken off of head when headed (no pun intended) into a major release. However, it is good that you reported this, so the /etc/rc.d/nfsserver issue can get resolved. rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel?
Steve Kargl wrote: > So, I upgraded a system from Feb 10 -current to today's > -current code. In doing so, I changed the kernel config > options from > > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > > to > > options NFSCL # Network Filesystem Client > options NFSD # Network Filesystem Server > > rebuild and install the kernel. Upon rebooting, I'm greeted > with a > > Jul 6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > kernel module nfsserver > > Of course, it can't load nfsserver because I don't use modules > nor build them. So, why is the system trying to load a nfsserver > module? Because, my /etc/rc.conf contains > > nfs_client_enable="YES" > nfs_server_enable="YES" > > if I change this to > > nfs_client_enable="YES" > nfsv4_server_enable="YES" > > The system no longer tries to load nfsserver upon rebooting. > Unfortunately, this has the effect that no nfsd daemons are > started. Well, I can start the daemons post-booting. > > node16:root[139] /etc/rc.d/nfsd start > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or > use 'onestart' instead of 'start'. > Assuming you've upgraded your /etc/rc.d scripts to those in head, then try deleting /etc/rc.d/nfsserver. (This script just tries to load the old server even though you don't need it unless you want to run the old one.) Or you can build a kernel with both options NFSD options NFSSERVER to make it happy. I'll try posting to rc@ to see if I can get rid of /etc/rc.d/nfsserver. Thanks for pointing this out. I had forgotten about deleting this (and was until recently confused about when obsolete files get deleted). If you still have problems after deleting /etc/rc.d/nfsserver (assuming your /etc/rc.d scripts are up-to-date), please let me know. rick ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel?
On Wed, Jul 06, 2011 at 05:02:37PM -0700, Garrett Cooper wrote: > On Wed, Jul 6, 2011 at 4:57 PM, Steve Kargl > wrote: > > So, I upgraded a system from Feb 10 -current to today's > > -current code. ?In doing so, I changed the kernel config > > options from > > > > options ? ? ? ? NFSCLIENT ? ? ? ? ? ? ? # Network Filesystem Client > > options ? ? ? ? NFSSERVER ? ? ? ? ? ? ? # Network Filesystem Server > > > > to > > > > options ? ? ? ? NFSCL ? ? ? ? ? ? ? ?# Network Filesystem Client > > options ? ? ? ? NFSD ? ? ? ? ? ? ? ? # Network Filesystem Server > > > > rebuild and install the kernel. ?Upon rebooting, I'm greeted > > with a > > > > Jul ?6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > > kernel module nfsserver > > > > Of course, it can't load nfsserver because I don't use modules > > nor build them. ?So, why is the system trying to load a nfsserver > > module? ?Because, my /etc/rc.conf contains > > > > nfs_client_enable="YES" > > nfs_server_enable="YES" > > > > if I change this to > > > > nfs_client_enable="YES" > > nfsv4_server_enable="YES" > > > > The system no longer tries to load nfsserver upon rebooting. > > Unfortunately, this has the effect that no nfsd daemons are > > started. ?Well, I can start the daemons post-booting. > > > > node16:root[139] /etc/rc.d/nfsd start > > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or use > > 'onestart' instead of 'start'. > > Try nfsserver instead of nfsd. Here's the archived discussion of > my foray into this territory a few months ago: > http://www.mailinglistarchive.com/html/freebsd-current@freebsd.org/2011-05/msg8.html > . Thanks for the pointer. Note, the 20110427 src/UPDATING entry indicates the NFSSERVER has been changed to NFSD in GENERIC. It seems that one needs to have both nfs_server_enable and nfsv4_server_enable set to "YES" in rc.conf to get nfsd daemons started. This is POLA violation for anyone upgrading from pre-20110427 -current and carrying over their old /etc/rc.conf. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can options NFSD and NFSSERVER exist in the same kernel?
On Wed, Jul 6, 2011 at 4:57 PM, Steve Kargl wrote: > So, I upgraded a system from Feb 10 -current to today's > -current code. In doing so, I changed the kernel config > options from > > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > > to > > options NFSCL # Network Filesystem Client > options NFSD # Network Filesystem Server > > rebuild and install the kernel. Upon rebooting, I'm greeted > with a > > Jul 6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load > kernel module nfsserver > > Of course, it can't load nfsserver because I don't use modules > nor build them. So, why is the system trying to load a nfsserver > module? Because, my /etc/rc.conf contains > > nfs_client_enable="YES" > nfs_server_enable="YES" > > if I change this to > > nfs_client_enable="YES" > nfsv4_server_enable="YES" > > The system no longer tries to load nfsserver upon rebooting. > Unfortunately, this has the effect that no nfsd daemons are > started. Well, I can start the daemons post-booting. > > node16:root[139] /etc/rc.d/nfsd start > Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or use > 'onestart' instead of 'start'. Try nfsserver instead of nfsd. Here's the archived discussion of my foray into this territory a few months ago: http://www.mailinglistarchive.com/html/freebsd-current@freebsd.org/2011-05/msg8.html . Cheers! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
