From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/netifrc:master commit in: init.d/
Date: Mon, 25 May 2015 10:04:19 +0000 (UTC) [thread overview]
Message-ID: <1426004089.902d48c8bd46dd67565371cb5d2c84f91ad30b8e.vapier@OpenRC> (raw)
commit: 902d48c8bd46dd67565371cb5d2c84f91ad30b8e
Author: Thomas D <whissi <AT> whissi <DOT> de>
AuthorDate: Wed Apr 16 09:52:56 2014 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Mar 10 16:14:49 2015 +0000
URL: https://gitweb.gentoo.org/proj/netifrc.git/commit/?id=902d48c8
_wait_for_carrier(): Workaround for output when using rc_parallel="YES" is no longer needed
_wait_for_carrier() was using a workaround when rc_parallel is enabled.
This caused the following broken output:
https://bugs.gentoo.org/attachment.cgi?id=361054
This patch fixes bug 488256 by removing the workaround, because this
workaround isn't needed anymore.
X-Gentoo-Bug: 488256
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=488256
init.d/net.lo.in | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/init.d/net.lo.in b/init.d/net.lo.in
index bdb3747..e883f98 100644
--- a/init.d/net.lo.in
+++ b/init.d/net.lo.in
@@ -116,7 +116,7 @@ _flatten_array()
_wait_for_carrier()
{
- local timeout= efunc=einfon
+ local timeout=
_has_carrier && return 0
@@ -126,20 +126,19 @@ _wait_for_carrier()
# Incase users don't want this nice feature ...
[ ${timeout} -le 0 ] && return 0
- yesno ${RC_PARALLEL} && efunc=einfo
- ${efunc} "Waiting for carrier (${timeout} seconds) "
+ einfon "Waiting for carrier (${timeout} seconds) "
while [ ${timeout} -gt 0 ]; do
if _has_carrier; then
- [ "${efunc}" = "einfon" ] && echo
+ echo
eend 0
return 0
fi
sleep 1
: $(( timeout -= 1 ))
- [ "${efunc}" = "einfon" ] && printf "."
+ printf "."
done
- [ "${efunc}" = "einfon" ] && echo
+ echo
eend 1
return 1
}
next reply other threads:[~2015-05-25 10:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 10:04 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-07 9:42 [gentoo-commits] proj/netifrc:master commit in: init.d/ Sam James
2021-03-31 1:11 Patrick McLean
2020-09-07 13:03 Lars Wendler
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2019-04-21 5:34 Robin H. Johnson
2017-11-14 20:48 Robin H. Johnson
2017-11-14 20:48 Robin H. Johnson
2016-10-24 20:52 Robin H. Johnson
2016-10-24 0:23 Robin H. Johnson
2016-10-24 0:23 Robin H. Johnson
2016-10-23 23:50 Robin H. Johnson
2016-07-05 18:13 Robin H. Johnson
2015-11-08 14:30 Robin H. Johnson
2015-11-08 14:30 Robin H. Johnson
2015-05-25 10:01 Mike Frysinger
2015-01-09 17:17 Robin H. Johnson
2014-10-11 19:47 Robin H. Johnson
2014-07-17 17:56 Robin H. Johnson
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=1426004089.902d48c8bd46dd67565371cb5d2c84f91ad30b8e.vapier@OpenRC \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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