Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!newsserver.jvnc.net!yale.edu!yale!gumby!destroyer!news.itd.umich.edu!news.itd.umich.edu!not-for-mail
From: pauls@terminator.rs.itd.umich.edu (Paul Southworth)
Newsgroups: comp.os.386bsd.questions
Subject: nfsiod -- necessary?
Date: 6 Jul 1993 10:01:36 -0400
Organization: Information Technology Division, University of Michigan
Lines: 18
Distribution: world
Message-ID: <21c0k0$n7o@terminator.rs.itd.umich.edu>
NNTP-Posting-Host: terminator.rs.itd.umich.edu
Gee, nfsiod processes running away like crazy, so I turn them off and
things seem to work ok. According to the man page:
Nfsiod runs on an NFS client machine to service asynchronous I/O requests
to its server. It improves performance but is not required for correct
operation. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The option numdaemons defines how many nfsiod daemons to start;
if unspecified, only a single daemon will be started. A client
should typically run enough daemons to handle their maximum level
of concurrency, typically four to six.
So given that, why run nfsiod? Seems like given the situation -- a simple
client with a single user -- sorting out adequate numbers of concurrent
threads is not a problem.