On Fri, 11 Feb 2005 20:52:37 +1300, Mark Carey <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] mark]# time exportfs -r
> exportfs: No 'sync' or 'async' option specified for export
> "192.168.10.0/255.255.255.0:/home".
> Assuming default behaviour ('sync').
> NOTE: this default has changed from previous versions
>
> real 1m20.015s
> user 0m0.003s
> sys 0m0.007s
Note on further testing adding sync to /etc/exports does remove the
warning but it does change the startup time.
> While reading the manpage for exportfs I got a bit curious, mountd
> appears to maintain a list of servers currently authenticated to use
> the shares stored in /var/lib/nfs/xtab and interestingly enough with
> no other computers active on the network this file shows two entries
> ....
>
> [EMAIL PROTECTED] mark]# cat /var/lib/nfs/xtab
> /home
> 192.168.10.250(rw,sync,wdelay,hide,secure,no_root_squash,no_all_squash,subtree_check,secure_locks,mapping=identity,anonuid=-2,anongid=-2)
> /home
> 192.168.10.252(rw,sync,wdelay,hide,secure,no_root_squash,no_all_squash,subtree_check,secure_locks,mapping=identity,anonuid=-2,anongid=-2)
>
> Does having these two mystery entries effect startup performance,
> maybee, how do I clean them out? Ok nfs gurus how do I strip these
> out of the mountd's cache, hand edit the file /var/lib/nfs/xtab?
No you read the documentation further and find out what exportfs -a does.
However after taking this step nfs is still slow to start up.
Can anyone else comment on their nfs startup times?
Do I need to be running name resolution during nfs startup? I can see
any reason why, however this is pure speculation, am I wrong?
Mark
