On Monday, October 28, 2002, at 06:49 PM, Andy Bastien wrote:
That sums it up quite nicely. The aforementioned NFS Manager is a more guiding GUI to these settings. If you prefer to work with configuration files, OTOH, it is also possible to load the settings from a NetInfo dump file withIn NetInfo (I'm sure you can use either niutil or NetInfo Manager...I used NetInfo Manager) create the directory /config/nfsd and add an arguments property. You can set arguments blank, but I use '-t -u -n 3' because I have a very low usage level.Also in NetInfo, create /exports. Under /exports, create a directory for each export you want to make. The name property of each directory is the directory you're exporting, (e.g. '/exports/foobar'). Create a clients property and give it a list of the clients that can connect (I never got this working with a network such as 192.168.1.0/24 or 192.168.1.0/255.255.255.0, so I'm not sure how you do that). Also create an opts property. I don't know what are the valid options...I've seen a few references to look in the exports man page, but you apparently don't get one unless you get OSX Server. Setting it blank works for my needs. Start up portmapper, if it isn't already running, with '/System/Library/StartupItems/Portmap/Portmap start', and start the NFS server with '/System/Library/StartupItems/NFS/NFS start'. When you update the exports list, use 'killall -HUP mountd' to tell the NFS server to re-read the export list.
'niload -r /exports . < exports.nidump'
where a typical example of a property list for exports could look like:
{
"name" = ( "exports" );
CHILDREN = (
{
"name" = ( "/Volumes/Users" );
"clients" = ( "host1", "host2" );
"opts" = ( "alldirs", "maproot=nobody" );
},
{
"name" = ( "/Volumes/Data" );
"clients" = ( "host1" );
"opts" = ( "alldirs" );
}
)
}
This also gives some examples of valid options, in particular "maproot=nobody" is usually a sensible security measure. I think probably all common options for NFS version 3 are supported, so if you can get your hands on a Linux, or better yet, *BSD manpage, you should be fine. It should also be said that Darwin's implementation of NFS 3 is still quite crappy, e.g. file access beyond 2 GB does not work (at least not with mounts from OS X, I have not tested this with exporting to a different Unix).
Derek
--
------------------------------------------------------------------------ -
Derek Homeier
Department of Physics & Astronomy and Center for Simulational Physics
University of Georgia Phone: ++1 (706) 583 8226
Athens, GA 30602-2451, USA Fax: ++1 (706) 542 2492
http://dilbert.physast.uga.edu/~derek/ Email: [EMAIL PROTECTED]
------------------------------------------------------------------------ -
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
