From: Amit Gud <agud@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: Neil Brown <neilb@suse.de>,
gud@eth.net, nfs@lists.sourceforge.net,
Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH 1 / 1] Move NFS mount code from util-linux to nfs-utils - take2
Date: Mon, 12 Jun 2006 23:15:02 -0400 [thread overview]
Message-ID: <448E2DB6.6050209@redhat.com> (raw)
In-Reply-To: <1150165495.3061.19.camel@raven.themaw.net>
Ian Kent wrote:
> On Mon, 2006-06-12 at 19:06 -0400, Amit Gud wrote:
>> Neil,
>>
>> It avoids code duplication (of parsing the options and error checking)
>> if we don't branch two different binaries for the NFSv4 and older versions.
>>
>
>> +
>> + if(!nomtab)
>> + add_mtab(spec, mount_point, nfs_mount_vers == 4 ? "nfs4" : "nfs",
>> + flags, extra_opts, 0, 0);
>
> If mtab~ is busy won't this cause mtab to get out of sync?
>
Cannot really spin over until the file lock is achieved, it may
potentially never be.
AG
--
May the source be with you.
http://www.cis.ksu.edu/~gud
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-06-13 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 23:06 [PATCH 1 / 1] Move NFS mount code from util-linux to nfs-utils - take2 Amit Gud
2006-06-13 2:24 ` Ian Kent
2006-06-13 3:15 ` Amit Gud [this message]
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=448E2DB6.6050209@redhat.com \
--to=agud@redhat.com \
--cc=SteveD@redhat.com \
--cc=gud@eth.net \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=raven@themaw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox