All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] split out nfs rpc process startup
Date: Mon, 30 Jan 2012 16:39:10 +0800	[thread overview]
Message-ID: <4F26572E.7030806@redhat.com> (raw)
In-Reply-To: <jg5jov$3qk$2@dough.gmane.org>

On 01/30/2012 04:18 PM, Cong Wang wrote:

> On Mon, 30 Jan 2012 at 06:43 GMT, Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> Index: dracut/modules.d/95nfs/nfs-start-rpc
>> ===================================================================
>> --- /dev/null
>> +++ dracut/modules.d/95nfs/nfs-start-rpc
>> @@ -0,0 +1,22 @@
>> +#!/bin/sh
>> +# -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*-
>> +# ex: ts=8 sw=4 sts=4 et filetype=sh
>> +
>> +nfsstart() {
>> +    # Start rpcbind or rpcbind
>> +    # FIXME occasionally saw 'rpcbind: fork failed: No such device' -- why?
>> +    command -v portmap >/dev/null && [ -z "$(pidof portmap)" ] && portmap
>> +    command -v rpcbind >/dev/null && [ -z "$(pidof rpcbind)" ] && rpcbind
>> +
>> +    if [ "$1" = "nfs4" ]; then
>> +        [ ! -d /var/lib/nfs/rpc_pipefs/nfs ] && \
>> +             mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs
>> +
>> +        # Start rpc.statd as mount won't let us use locks on a NFSv4
>> +        # filesystem without talking to it. NFSv4 does locks internally,
>> +        # rpc.lockd isn't needed
>> +        [ -z "$(pidof rpc.statd)" ] && rpc.statd
>> +
>> +        [ -z "$(pidof rpc.idmapd)" ] && rpc.idmapd
>> +    fi
>> +}
>> Index: dracut/modules.d/95nfs/nfsroot
>> ===================================================================
>> --- dracut.orig/modules.d/95nfs/nfsroot
>> +++ dracut/modules.d/95nfs/nfsroot
>> @@ -84,22 +84,10 @@ getarg rw && nfsrw=rw
>>  
>>  options=${options:+$options,}$nfsrw
>>  
>> -# Start rpcbind or rpcbind
>> -# FIXME occasionally saw 'rpcbind: fork failed: No such device' -- why?
>> -command -v portmap >/dev/null && [ -z "$(pidof portmap)" ] && portmap
>> -command -v rpcbind >/dev/null && [ -z "$(pidof rpcbind)" ] && rpcbind
>> +. /sbin/nfs-start-rpc
>> +nfsstart $nfs
> 
> Huh? Why making nfsstart a function and source it here?
> Why not just make nfsstart as a script and invoke that script here?
> This reads odd to me.


no special reason for this, I'm fine to make it a script

> 
> --
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Thanks
Dave

  reply	other threads:[~2012-01-30  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  6:43 [PATCH] split out nfs rpc process startup Dave Young
2012-01-30  8:18 ` Cong Wang
2012-01-30  8:39   ` Dave Young [this message]
     [not found]     ` <4F26572E.7030806-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30  8:38       ` Cong Wang
     [not found]         ` <4F265712.7090302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30  9:03           ` Dave Young

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=4F26572E.7030806@redhat.com \
    --to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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.