From: Chuck Lever <chuck.lever@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH 10/10] mount.nfs: Fix background mounts
Date: Mon, 06 Aug 2007 20:31:29 -0400 [thread overview]
Message-ID: <46B7BD61.7060304@oracle.com> (raw)
In-Reply-To: <18103.46593.586196.718154@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
Neil Brown wrote:
> On Tuesday August 7, sgunderson@bigfoot.com wrote:
>> On Fri, Aug 03, 2007 at 01:24:15PM -0400, Chuck Lever wrote:
>>> The new mount.nfs helper does not support background mounts. Add support
>>> for background mounts.
>> I've now pushed the current git (which includes these patches) into Debian,
>> which will hopefully give us some experience with "bg" again. It seems to
>> have fixed some bugs of the old bg implementation, but this one still
>> remains:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144185
>>
>> Any chance mount.nfs could simply ignore HUPs?
>>
>> /* Steinar */
>> --
>> Homepage: http://www.sesse.net/
>
> Something like this? Anyone want to test it?
>
> NeilBrown
I copied the "bg" logic straight from util-linux, then simplified it.
Using daemon() instead of fork() seems like a nice clean-up anyway.
(It's just me, but I like a blank between the first and second argument
of daemon() -- that matches the coding style in the rest of that file).
Steinar, it's not clear to me from the Debian bug report whether this is
really a mount bug or an init scripts bug. I assume this is something
that did not work correctly for the legacy util-linux mount command either?
> diff --git a/utils/mount/mount.c b/utils/mount/mount.c
> index a232519..5769cd2 100644
> --- a/utils/mount/mount.c
> +++ b/utils/mount/mount.c
> @@ -530,9 +530,7 @@ int main(int argc, char *argv[])
> * Parent exits immediately with success. Make
> * sure not to free "mount_point"
> */
> - if (fork() > 0)
> - exit(0);
> -
> + daemon(0,0);
> mnt_err = try_mount(spec, mount_point, flags, fs_type,
> &extra_opts, mount_opts, fake,
> nomtab, BACKGROUND);
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-07 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 17:24 [PATCH 10/10] mount.nfs: Fix background mounts Chuck Lever
2007-08-06 22:31 ` Steinar H. Gunderson
2007-08-07 0:00 ` Neil Brown
2007-08-07 0:31 ` Chuck Lever [this message]
2007-08-09 19:16 ` Steinar H. Gunderson
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=46B7BD61.7060304@oracle.com \
--to=chuck.lever@oracle.com \
--cc=neilb@suse.de \
--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.