From: Ian Kent <raven@themaw.net>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: autofs5 early daemonization side effects
Date: Thu, 19 Mar 2009 00:59:35 +0900 [thread overview]
Message-ID: <49C11A67.5000603@themaw.net> (raw)
In-Reply-To: <x49sklahpfx.fsf@segfault.boston.devel.redhat.com>
Jeff Moyer wrote:
> Leonardo Chiquitto <leonardo.lists@gmail.com> writes:
>
>> Hello,
>>
>> I've been doing some tests with AutoFS5 and I'd like to confirm that
>> the behavior I'm seeing during the daemon initialization is expected
>> or not.
>>
>> The problem: when the autofs initscript returns, autofs is not really
>> ready.
>
> Strange. I originally wrote the code to return a status via a pipe, so
> that the init script would not return status until the daemon was ready
> to service requests. It also took care of the problem of the init
> script returning success when the daemon actually failed.
>
> Ian, has this changed?
No, but there was a problem with the read size on x86_64, which has also
been fixed. I'm not sure if that was a transcription error on my part or
not.
The other possibility is that the handle_mounts() thread creation could
be returning before it has completed its initialisation. But looking at
the code I can't see that happening either, certainly not before the
mount is done and the map read, if in fact it needs to be read (which,
as you know, it isn't for the most common configuration).
Ian
next prev parent reply other threads:[~2009-03-18 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 14:10 autofs5 early daemonization side effects Leonardo Chiquitto
2009-03-18 14:27 ` michael
2009-03-18 14:32 ` Jeff Moyer
2009-03-18 15:59 ` Ian Kent [this message]
2009-03-18 20:39 ` Leonardo Chiquitto
2009-03-23 20:42 ` michael
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=49C11A67.5000603@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=jmoyer@redhat.com \
/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.