Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 05-14-2004, 08:48 PM   #1
Registered: Jul 2003
Location: Dallas, TX
Distribution: Ubuntu 10.04 LTS
Posts: 987

Rep: Reputation: 30
nfsd will not start

running kernel 2.6.5 with slackware-current

i built the kernel with nfs file system support using nfs version 3

i have modfied my exports, host.allow and hosts.deny files, but running rc.nfsd (after starting rc.portmap) yields the following output:

root@darkstar:/etc/rc.d# ./rc.nfsd start
FATAL: Module nfsd not found.
Starting NFS services:
/usr/sbin/exportfs -r Function not implemented Function not implemented
/usr/sbin/rpc.nfsd 8
lockdsvc: Function not implemented

afaik, there is no such nfsd module in the 2.6 kernels, but i can modprobe nfs without a problem, but the nfsd script still will not function

is there an explicit way that i should start nfs or is there another problem?
i have even tried with an empty hosts.deny file

here is my hosts.allow:


*EDIT: omg, what a moron.... i completely missed the nfs server option in kernel config... oops
i'll recompile and hopefully that will get everything working

*edit 2: ya, everything is working now (nfsd is the nfs server kernel module)
i have to say, this system is awesome, i've never had such an easily setup and flawless network!

Last edited by TheOneAndOnlySM; 05-15-2004 at 12:00 AM.
Old 06-08-2004, 03:41 PM   #2
Registered: Jan 2003
Location: Ballston Lake, NY
Distribution: Slackware, Debian
Posts: 662

Rep: Reputation: 30
I was gonna say, another classic example of where slackware likes modules as opposed to compiled into the kernel.
Old 06-08-2004, 07:19 PM   #3
Registered: Jul 2003
Location: Dallas, TX
Distribution: Ubuntu 10.04 LTS
Posts: 987

Original Poster
Rep: Reputation: 30
less the idea that slackware itself likes modules, but the startup scripts do, simply because a lot of the things the startup scripts modprobe are things that are not absolutely necessary to run the computer

but then again, slackware's startup scripts are easily modifiable to just remove the modprobe nfsd lines and let the script start the nfsd services (portmapper, etc); it wouldn't complain because as these calls are made, the kernel will know what to do

nfs(d) is a good idea to compile as module if you know that it will not be necessary every time; if you are running a dedicated nfs server, then it would be a decent idea to compile into the kernel (though it will definitely do some enlargement....)

but it probably wouldn't matter because if i was running a dedicated file server, nfs server, then i wouldn't even include sound, video, or usb/firewire support, but simply basic necessities and net support


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
NFSd fails to start due to RPC? TexasDex Linux - Software 10 03-23-2010 03:02 AM
no nfsd process linuxhippy Slackware 3 05-06-2005 07:21 PM
can not export per nfsd blish_blash *BSD 1 12-26-2004 02:13 PM
Problem with NFS : nfsd daeom fail mabs Linux - Networking 5 07-28-2003 10:53 PM
nfsd Input/output errror padlamoij Slackware 2 12-13-2002 12:05 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:37 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration