linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH nfs-utils] nfs-server-generator: avoid using external services.
Date: Tue, 1 Nov 2016 18:03:12 -0400	[thread overview]
Message-ID: <d58fc30b-bd9a-c280-c8a3-0358e9f1de01@RedHat.com> (raw)
In-Reply-To: <87wpgnq8jx.fsf@notabene.neil.brown.name>



On 11/01/2016 03:55 PM, NeilBrown wrote:
> On Wed, Nov 02 2016, Steve Dickson wrote:
> 
>> Hello,
>>
>> On 10/13/2016 02:50 AM, NeilBrown wrote:
>>>
>>> nfs-server-generator is run very early when a lot of services
>>> are not yet started, so it mustn't depend on them.
>>> Currently it can try to use hostname lookup and syslog.
>>>
>>> Hostname-lookup is not needed, as we don't use the host issue,
>>> and sending message to stderr is sufficient for the generator.
>>>
>>> Disabling syslog is easy - call a function that sets a static variable.
>>>
>>> Disabling hostname lookup isn't quite so easy, so add a static variable
>>> which can be set to disable it.
>>>
>>> Signed-off-by: NeilBrown <neilb@suse.com>
>>> ---
>>>
>>> hi,
>>>  I contemplated passing another arg to export_read() and export_d_read()
>>>  to resolve this, but it didn't seem worth it.
>>>
>>>  Is this approach OK to people?
>> It's not the most eloquent interface I've 
>> ever seen... ;-) 
>>
>> What are the failures this is fixing? When a
>> hostname lookup is done what happens? Failure
>> hangs stopping the server from coming up?
> 
>  I never actually reproduced it myself, but I think that when hostname
>  lookup failed (possibly after a timeout) it tried to log an error via
>  syslog and writing to syslog blocked indefinitely.
>  The systemd.generator manpage explicitly rules out trying to talk to
>  syslog.
This makes sense... 

> 
> 
>>
>>  
>>>
>>> Thanks,
>>> NeilBrown
>>>
>>>
>>>  support/export/export.c        | 12 ++++++++++--
>>>  support/include/exportfs.h     |  1 +
>>>  systemd/nfs-server-generator.c |  4 ++++
>>>  3 files changed, 15 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/support/export/export.c b/support/export/export.c
>>> index 0b8a858c2c74..c65dc8807a4e 100644
>>> --- a/support/export/export.c
>>> +++ b/support/export/export.c
>>> @@ -67,6 +67,14 @@ static void warn_duplicated_exports(nfs_export *exp, struct exportent *eep)
>>>  	}
>>>  }
>> If we do have to stay with this approach, 
>> I definitely think comment explaining
>> why its needed and what it does.
> 
> That's sensible.  I'll resend with some nice friendly comments.
Thanks! 

> 
>>
>> Finally, on an unrelated issue I'm seeing 
>> SELinux preventing nfs-server-generator from 
>> accessing nfs-server.service.d/order-with-mounts.conf
>> because of a labeling issue. I guess the label
>> should be nfsd_unit_file_t not systemd_unit_file_t
> 
> I wouldn't know about that :-(
I'll figure this out... 

steved.

> 
> Thanks,
> NeilBrown
> 

  reply	other threads:[~2016-11-01 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  6:50 [PATCH nfs-utils] nfs-server-generator: avoid using external services NeilBrown
2016-11-01 18:45 ` Steve Dickson
2016-11-01 19:55   ` NeilBrown
2016-11-01 22:03     ` Steve Dickson [this message]
2016-11-02  0:25       ` [PATCH nfs-utils v2] " NeilBrown
2016-11-07 19:16         ` Steve Dickson

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=d58fc30b-bd9a-c280-c8a3-0358e9f1de01@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).