| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Resolves: #1773798
|
| |
|
| |
|
|
|
| |
Resolve: BZ #1691552
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
See https://bugzilla.redhat.com/show_bug.cgi?id=1584317 for more info.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This was causing the /etc/resolv.conf file to be always updated when
RESOLV_MODS was not set...
Before the commit 5d6156454bf8f6dab4a5fdd7e1bf6 we were not updating
the /etc/resolv.conf file if the RESOLV_MODS was empty.
See https://bugzilla.redhat.com/show_bug.cgi?id=1610411 for more info.
|
| |
|
|
|
|
|
|
|
| |
This partially reverts the commit 15eaf7ece, because systemd's
generated unit files might have incorrect dependencies at some
circumstances, thus causing diskless nfs-clients to hang while
unmounting root filesystem after '$ service network stop'.
|
|
|
|
|
|
| |
Since we are using systemd, the Default-Start/Stop keywords were
omitted. Basically the LSB header is quite similar to LSB header of
network service...
|
|
|
|
|
|
|
|
|
|
| |
Previously, there were 2 additional conditions related to this part of
code, but they were removed in time, so this last condition has
remained an artifact and is de-facto obsolete.
However, the 'pidof -x dhclient' condition could cause the network
service to hang on stop/restart when processes were executed from a
network share... Removing that condition should hypothetically fix it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For currently unknown reason the dbus-send calls will fail to set the
firewall zone for the given interface if we omit the --print-reply
option...
This looks like some kind of race-condition in dbus-send, since the
--print-reply makes the call synchronous and slower.
Hopefully this is only a temporary workaround until DBus is fixed.
Resolves: #1586284
|
| |
|
|
|
|
| |
Resolves: RHBZ#1583677
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This can be useful when user has this UEFI boot order e.g.:
Windows | grub | Linux
And decides to boot into grub/Linux. In case the autorelabel service
is being run after the boot into grub, then the reboot after the
autorelabel is done will cause user to boot into Windows again...
This change should make the behaviour more intuitive for the user.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
network-functions uses awk to tranform the mac address to upper case.
Replace awk with tr which is two order of magnitude faster:
$ time awk '{ print toupper($0) }' </usr/share/dict/words >/dev/null
real 0m0,227s
user 0m0,224s
sys 0m0,004s
$ time tr '[a-z]' '[A-Z]' </usr/share/dict/words >/dev/null
real 0m0,005s
user 0m0,000s
sys 0m0,005s
Also use here-strings instead of spawning a subshell and a pipe.
Signed-off-by: Matteo Croce <mcroce@redhat.com>
|
|
|
|
|
| |
... Without appending the 'ro' to mount options of '/' mount point the
system will be still mounted as read-write, even when READONLY=yes.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of displaying messages without context, like this:
./network-functions: line 571: echo: write error: Invalid argument
./network-functions: line 598: echo: write error: Permission denied
We will now display pretty error messages (via net_log) about what has
actually failed...
This has been requested by our customer:
https://bugzilla.redhat.com/show_bug.cgi?id=1542514
|
|
|
|
|
| |
They have sane default values in kernel for IBM machines as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1493069
|
|
|
|
| |
More info: https://bugzilla.redhat.com/show_bug.cgi?id=1554690
|
|
|
|
| |
Resolves: #1553093
|
|
|
|
| |
More info: https://bugzilla.redhat.com/show_bug.cgi?id=1518429
|
| |
|
|
|
|
|
|
|
| |
Empty ${RESOLV_MODS} was causing a deletion of config files in
/etc/ppp/peers/*
Resolves: #155
|
| |
|
| |
|
|
|
|
|
| |
Also, add a conflict for older versions of 'redhat-release'. Using
them would cause unbootable system most likely...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is complete rework of how we generate the /etc/resolv.conf.
Fixes:
* always update 'nameserver' & 'search' entries when DNS* & DOMAIN
options (respectively) were updated in ifcfg-* files
* always update the order of 'nameserver' entries when the order of
DNS* options was updated
Enhancements:
* added support for DNS3 option (equals to MAXNS value in GLIBC)
* added logic to process duplicate DNS* options
* added logic to process randomly omitted DNS* options (e.g. omitting
DNS1 while specifying DNS2 and/or DNS3 will still work now)
This work was based on these two RHEL-7.5 BZs:
https://bugzilla.redhat.com/show_bug.cgi?id=1364895
https://bugzilla.redhat.com/show_bug.cgi?id=1357658
|
|
|
|
|
|
|
|
| |
The symlinks are no longer needed. Enablement of default services
is now managed by 'redhat-release' package.
Resolves: #1395391
Resolves: #1357648
|
| |
|
|
|
|
|
| |
Otherwise obtaining IP from DHCP might fail. Based on patch from:
* Rich Alloway <richard.alloway@roguewave.com> | CentOS BZ #0011138
|
|
|
|
|
|
|
|
|
|
| |
And network-scripts/network-functions was patched to use convert2sec().
This function can be used to convert the value of its first parameter
to a number of seconds - based on the time unit (specified as the
second parameter).
This is mostly useful for converting values for use with the sleep(1).
|
|
|
|
|
| |
In some cases we are using "on" or "off" as values. is_true()
and is_false() can be used for evaluation of these values as well.
|
|
|
|
|
| |
The time units had to be manually converted from microseconds to
seconds. Hopefully this was done right.
|
| |
|
|
|
|
|
| |
To speed things up. Based on patch & comments from:
https://bugzilla.redhat.com/show_bug.cgi?id=1497759
|
| |
|
|
|
|
|
|
|
|
|
| |
The ARPUPDATE option has been introduced. It defaults to 'yes'.
By setting the ARPUPDATE to 'no', administrator can disable
updating neighbouring computers with ARP information about current
NIC. This is especially needed when using LVS Load Balancing with
Direct routing enabled.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The way DHCP_HOSTNAME is being sent to DHCP server has been completely
reworked...
DHCP_FQDN now allows user to specify fully qualified domain name to be
sent to DHCP server instead of just using simple hostname. This option
takes precedence before DHCP_HOSTNAME variable.
DHCP_SEND_HOSTNAME can be used to tell initscripts to not send either
DHCP_HOSTNAME or DHCP_FQDN to DHCP server.
Both of these options should behave same as they do in NetworkManager.
|
| |
|
| |
|