From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] add function wait_for_route_ok
Date: Wed, 15 Feb 2012 09:23:59 +0100 [thread overview]
Message-ID: <4F3B6B9F.3070203@redhat.com> (raw)
In-Reply-To: <20120215064029.GA30112-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
Am 15.02.2012 07:40, schrieb Dave Young:
> Manually setuping nic through udev is not always done when
> we want network access. Here add a function wait_for_route_ok to
> wait and make sure the network is accesible
>
> Signed-off-by: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> modules.d/99base/dracut-lib.sh | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/modules.d/99base/dracut-lib.sh b/modules.d/99base/dracut-lib.sh
> index 85d4925..c85a019 100755
> --- a/modules.d/99base/dracut-lib.sh
> +++ b/modules.d/99base/dracut-lib.sh
> @@ -392,6 +392,17 @@ wait_for_if_up() {
> return 1
> }
>
> +wait_for_route_ok() {
> + local cnt=0
> + while [ $cnt -lt 200 ]; do
> + li=$(ip route show)
> + [[ "$li" =~ "$1" ]] && return 0
> + sleep 0.1
> + cnt=$(($cnt+1))
> + done
> + return 1
> +}
> +
> # root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>]
> # root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>]
> nfsroot_to_var() {
$ li=$(ip route show)
$ [[ "$li" =~ "$1" ]] && echo OK
dash: 6: [[: not found
Please do not use "bash" syntax
next prev parent reply other threads:[~2012-02-15 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 6:40 [PATCH 3/3] add function wait_for_route_ok Dave Young
[not found] ` <20120215064029.GA30112-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2012-02-15 8:23 ` Harald Hoyer [this message]
[not found] ` <4F3B6B9F.3070203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-16 1:15 ` Dave Young
[not found] ` <4F3C58C3.6020103-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-16 1:39 ` 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=4F3B6B9F.3070203@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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