| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| |/
| |
| |
| |
| | |
Tag as initscripts-9.64-1
rc.d/init.d/network: Added ADSL type ( not present in fedora :
TOOD: See if this is upstreamable )
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
Tag as initscripts-9.63-1
In rc.d/init.d/functions, gprintf replaced as upstream does by echo.
TODO: See if we keep this or revert the behaviour
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
Tag as initscripts-9.62-1
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
Tag as initscripts-9.61-1
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
is_available returns 2
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
Tag as initscripts-9.60-1
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The current grep check (fgrep -sqx) in install_bonding_driver, to determine
whether bond master exists, fails when there are multiple bond masters.
The fix assumes that multiple bond masters are on different lines in the file
"/sys/class/net/bonding_masters", while they are in fact on the same line.
Since fgrep -sqx checks for the entire line,it will never match any one bond
master within the line and always fail if there are multiple bonds.
This patch improves the check by creating a new function, bond_master_exists()
to handle this and other conditions.
Orabug: 19897586
Signed-off-by: Ashish Samant <ashish.samant@oracle.com>
Signed-off-by: John Haxby <john.haxby@oracle.com>
Acked-by: Mukesh Kacker <mukesh.kacker@oracle.com>
|
|\ \
| |/
| |
| | |
Tag as initscripts-9.59-1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1162822
When ifup is called on an interface that has BOOTPROTO=dhcp, ifup-eth
will call network-functions:check_link_down() to wait for carrier on
the interface before starting dhclient. If the interface happens to be
a bridge device, carrier will not come on until at least one attached
device is in "forwarding" mode. If the bridge has STP enabled, it
takes at least $DELAY * 2 + 5 seconds (sometimes slightly longer) for
any attached device to go into forwarding mode.
However, check_link_down() will only wait for max(${LINKDELAY}, 5)
seconds for carrier, and there are *many* existing configs that have
STP enabled but no setting for LINKDELAY. Every one of those configs
will now fail to ifup the bridge device.
The solution implemented in this patch is for ifup-eth to set
LINKDELAY to at least ${DELAY} * 2 + 7 when the device is a bridge an
STP is enabled. Since check_link_down() returns within .5 sec of
carrier coming up, the worst effect this could have would be to take
longer to fail in the case of a config where carrier was *never* going
to come up. Otherwise, it will not create any more delay than is
already present in cases that currently work, and will cause many
other configs to become unbroken.
|
| | |
|
|\ \
| |/
| |
| | |
Tag as initscripts-9.56-1
|
| |
| |
| |
| |
| | |
Conflicts:
sysconfig/network-scripts/network-functions
|
| | |
|
| | |
|
| |
| |
| |
| | |
kudos to john.haxby@oracle.com
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Conflicts:
sysconfig/network-scripts/ifup-wireless
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I don't have time to properly adapt our other scripts to cope here,
so just revert for now.
Hopefully by Mageia 6 we can ditch these scripts completely in
favour of networkd... but time will tell.
In this restoration, I've dropped the xsupplicant support as
no such binary exists in Mageia.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These generally don't matter too much but they look bad.
This change should both log a bit more (tailored for network service runs
where newlines are suppressed - thus not quite as nice when running ifup
manually, but nicer in the journal log for network.service)
It should also handle some more cases where there is no DEVICE variable
(typically when the device is not present and the ifcfg- file does not
set it explicitly, or when it is set explicitly but it's not plugged in)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ifcfg-lo file typically does not contain a UUID and thus NetworkManager
will complain saying:
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
This just silences this message (code below requires that
the UUID is returned from NM via DBus)
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Tag as initscripts-9.55-1
Conflicts:
Makefile
lang.csh
lang.sh
po/Makefile
ppp/ip-down
ppp/ip-up
rc.d/init.d/network
service
sysconfig.txt
sysconfig/init
sysconfig/network-scripts/ifdown-ppp
sysconfig/network-scripts/ifup
sysconfig/network-scripts/ifup-eth
sysconfig/network-scripts/ifup-ippp
sysconfig/network-scripts/ifup-ppp
sysconfig/network-scripts/ifup-wireless
sysconfig/network-scripts/network-functions
sysctl.conf
systemd/fedora-storage-init
Notes:
ppp support was dropped upstream so we will need to merge
it into the ppp package as Fedora has done.
The fedora-storage-init stuff has been dropped. LVM+Raid
is typically initialised automatically now via udev rules
etc. We should try and follow suit, but may need to add
the legacy script back in for now.
|
| |
| |
| |
| |
| | |
Conflicts:
sysconfig/network-scripts/ifup-eth
|
| | |
|
| | |
|