From: "michael@kmaclub.com" <michael@kmaclub.com>
To: Leonardo Chiquitto <leonardo.lists@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: autofs5 early daemonization side effects
Date: Mon, 23 Mar 2009 13:42:39 -0700 [thread overview]
Message-ID: <49C7F43F.7060704@kmaclub.com> (raw)
In-Reply-To: <c2d0b6ec0903181339o1bf5ea2cv3c16125fc702a572@mail.gmail.com>
Leonardo Chiquitto wrote:
>> 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.
>
> The Autofs code is completely right. The problem I'm seeing is being
> caused by startproc, a wrapper to start daemons that some distros
> (like openSUSE) use.
>
> Applying the following pseudo-patch in the initscript makes everything
> work as it should:
>
> - /sbin/startproc $DAEMON $AUTOFS_OPTIONS
> + $DAEMON $AUTOFS_OPTIONS
>
> Ian and Jeff, thanks for the help and sorry for the noise. Michael,
> with luck this will be a valid workaround for you too!
Thanks,
That does seem to be working for me.
Michael
prev parent reply other threads:[~2009-03-23 20:42 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
2009-03-18 20:39 ` Leonardo Chiquitto
2009-03-23 20:42 ` michael [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=49C7F43F.7060704@kmaclub.com \
--to=michael@kmaclub.com \
--cc=autofs@linux.kernel.org \
--cc=leonardo.lists@gmail.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.