mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jiri Pirko <jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	amwang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [patch dracut v2] fix teamd exec in case config does not include devname
Date: Tue, 22 Jan 2013 15:35:43 +0100	[thread overview]
Message-ID: <50FEA3BF.1090309@redhat.com> (raw)
In-Reply-To: <1357826571-1877-1-git-send-email-jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>

Am 10.01.2013 15:02, schrieb Jiri Pirko:
> In case that configuration file did not include name of team device,
> teamd would not start. Fix this by adding "-t" parameter.
> 
> Signed-off-by: Jiri Pirko <jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>
> ---
> 
> v2->v1:
> -fixed bad order of args
> 	
> modules.d/40network/ifup.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/modules.d/40network/ifup.sh b/modules.d/40network/ifup.sh
> index 216b1e3..6c3133e 100755
> --- a/modules.d/40network/ifup.sh
> +++ b/modules.d/40network/ifup.sh
> @@ -187,7 +187,7 @@ if [ -e /tmp/team.info ]; then
>              fi
>          done
>          # Do not add slaves now
> -        teamd -d -U -n -f /etc/teamd/$teammaster.conf
> +        teamd -d -U -n -t $teammaster -f /etc/teamd/$teammaster.conf
>          for slave in $working_slaves; do
>              # team requires the slaves to be down before joining team
>              ip link set $slave down
> 

merged

      parent reply	other threads:[~2013-01-22 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 14:02 [patch dracut v2] fix teamd exec in case config does not include devname Jiri Pirko
     [not found] ` <1357826571-1877-1-git-send-email-jiri-rHqAuBHg3fBzbRFIqnYvSA@public.gmane.org>
2013-01-10 14:10   ` Cong Wang
2013-01-22 14:35   ` Harald Hoyer [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=50FEA3BF.1090309@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=amwang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jiri-rHqAuBHg3fBzbRFIqnYvSA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox