From: "Timothy G. Wesemann" <timwese@voicenet.com>
To: <nfs@lists.sourceforge.net>
Subject: Re: nfs: server X not responding, still trying
Date: Wed, 5 Nov 2003 13:03:45 -0500 [thread overview]
Message-ID: <086e01c3a3c7$2b2af200$de0167cf@voicenet.com> (raw)
In-Reply-To: 482A3FA0050D21419C269D13989C6113020AC622@lavender-fe.eng.netapp.com
>> the async mount option is not needed, as async is the default.
>the async export option is to be avoided.
If that is so, then why does my exportfs (from nfs-utils-1.0.6) state the
following when exporting?
=================================
exportfs: /etc/exports [4]: No 'sync' or 'async' option specified for
export "192.168.10.0/24:/jetstor/incoming".
Assuming default behaviour ('sync').
NOTE: this default has changed from previous versions
=================================
--
Tim Wesemann
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-11-05 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 16:34 nfs: server X not responding, still trying Lever, Charles
2003-11-05 18:03 ` Timothy G. Wesemann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 22:50 Lever, Charles
2003-11-04 16:08 Lever, Charles
2003-11-03 22:35 Timothy G. Wesemann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='086e01c3a3c7$2b2af200$de0167cf@voicenet.com' \
--to=timwese@voicenet.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.