On Tue, 03 Apr 2007, Neil Brown wrote:
> 3.1. SERVER STARTUP
>
>
> A/ mount -t nfsd /proc/fs/nfsd
> This filesystem needs to be mount before most daemons,
> particularly exportfs, mountd, svcgssd, idmapd.
> It could be mounted once, or the script that starts each daemon
> could test if it is mounted and mount it if not.
mount -t rpc_pipefs /var/lib/nfs/rpc_pipefs
This filesystem must be mounted before svcgssd and idmapd daemons.
>
> B/ svcgssd ; idmapd
> These supply services to nfsd and so should be started before
> rpc.nfsd. Where they come between mounting the nfsd filesystem
> and starting the nfsd server is not important.
> idmapd is only need for NFSv4 support.
[...]
>
> 3.2. CLIENT STARTUP
>
> A/ sm-notify
> This should be run shortly after boot and before any NFS
> filesystems are mounted with remote-locking support -
> filesystems can be mounted with "-o nolock" before sm-notify.
> This is appropriate for '/', '/usr', and '/var'.
Same here.
> B/ gssd ; idmapd
> (I need some guidance here).
Jan
--
Jan Rekorajski | ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC | -- TROOPS by Kevin Rubio
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs