From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core111, updated. 3b1c776259eba53514c6fa4c120d919b7f3f365e
Date: Thu, 01 Jun 2017 09:20:33 +0100 [thread overview]
Message-ID: <20170601082033.755D210853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, core111 has been updated
via 3b1c776259eba53514c6fa4c120d919b7f3f365e (commit)
from 949815f136a9b89fd4aca2cae7a0e216f4065088 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 3b1c776259eba53514c6fa4c120d919b7f3f365e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jun 1 10:15:18 2017 +0200
dhcpcd: fix delay after dhcp down.
this also cause a delay with some nic's that cannot set the mtu in up state.
(eg. e1000e)
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/networking/dhcpcd.exe | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/src/initscripts/networking/dhcpcd.exe b/src/initscripts/networking/dhcpcd.exe
index 6c1391d..a2cdc66 100644
--- a/src/initscripts/networking/dhcpcd.exe
+++ b/src/initscripts/networking/dhcpcd.exe
@@ -79,6 +79,7 @@ dhcpcd_down()
# Only if RED_TYPE=DHCP update /var/ipfire/red
if [ "$RED_TYPE" == "DHCP" ]; then
logger -p local0.info -t dhcpcd.exe[$$] "${interface} has been brought down"
+ rm -f /var/ipfire/red/active
run_subdir ${rc_base}/init.d/networking/red.down/
fi
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-06-01 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170601082033.755D210853C3@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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