<feed xmlns='http://www.w3.org/2005/Atom'>
<title>initscripts/sysconfig, branch 9.49.48</title>
<subtitle>Mageia fork of Fedora's Init Scripts</subtitle>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/'/>
<entry>
<title>ifup-post: fix incorrect condition for RESOLV_MODS</title>
<updated>2018-08-24T10:23:27+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-08-20T12:31:56+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=d7e9663a063e087cd9c77844f56d1c17e7a19402'/>
<id>d7e9663a063e087cd9c77844f56d1c17e7a19402</id>
<content type='text'>
  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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  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.
</pre>
</div>
</content>
</entry>
<entry>
<title>ifdown-eth: no longer needed 'pidof -x dhclient' condition removed</title>
<updated>2018-07-24T13:52:11+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-05-14T11:40:08+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=8f42fe8dfb7dd6c3c4c2e551237e0d8ea023620b'/>
<id>8f42fe8dfb7dd6c3c4c2e551237e0d8ea023620b</id>
<content type='text'>
  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.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  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.
</pre>
</div>
</content>
</entry>
<entry>
<title>network-scripts: setting of firewall ZONE fixed</title>
<updated>2018-06-07T12:26:23+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-06-06T17:19:11+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=d951e7c7d64c0378424b8b2edd406ae9eaa73ec1'/>
<id>d951e7c7d64c0378424b8b2edd406ae9eaa73ec1</id>
<content type='text'>
  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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  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
</pre>
</div>
</content>
</entry>
<entry>
<title>network-functions: use tr to upper case strings rather than awk</title>
<updated>2018-05-17T15:47:07+00:00</updated>
<author>
<name>Matteo Croce</name>
<email>mcroce@redhat.com</email>
</author>
<published>2018-04-09T22:48:11+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=c29fbec03a13d7cfaac46af72aafc44f78902cc4'/>
<id>c29fbec03a13d7cfaac46af72aafc44f78902cc4</id>
<content type='text'>
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) }' &lt;/usr/share/dict/words &gt;/dev/null

    real    0m0,227s
    user    0m0,224s
    sys     0m0,004s
    $ time tr '[a-z]' '[A-Z]' &lt;/usr/share/dict/words &gt;/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 &lt;mcroce@redhat.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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) }' &lt;/usr/share/dict/words &gt;/dev/null

    real    0m0,227s
    user    0m0,224s
    sys     0m0,004s
    $ time tr '[a-z]' '[A-Z]' &lt;/usr/share/dict/words &gt;/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 &lt;mcroce@redhat.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>sysconfig/readonly-root: Clarify the usage of readonly-root.</title>
<updated>2018-05-17T13:18:03+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-05-10T15:18:54+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=402e41490782fc0549326be1a5d98bfa1f4ce35b'/>
<id>402e41490782fc0549326be1a5d98bfa1f4ce35b</id>
<content type='text'>
  ... Without appending the 'ro' to mount options of '/' mount point the
  system will be still mounted as read-write, even when READONLY=yes.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  ... Without appending the 'ro' to mount options of '/' mount point the
  system will be still mounted as read-write, even when READONLY=yes.
</pre>
</div>
</content>
</entry>
<entry>
<title>network-functions: add error messages for bonding installation</title>
<updated>2018-05-17T12:49:45+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-05-02T13:53:04+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=e811abf000f525932f6334ce0c06adb3d2860a6d'/>
<id>e811abf000f525932f6334ce0c06adb3d2860a6d</id>
<content type='text'>
  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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  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
</pre>
</div>
</content>
</entry>
<entry>
<title>ifdown-post: fix logical error in commit 5d61564</title>
<updated>2018-01-02T16:29:40+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2018-01-02T14:47:30+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=2caa3bfbe717f92d0e0677ea3dc1290a54a8bcf7'/>
<id>2caa3bfbe717f92d0e0677ea3dc1290a54a8bcf7</id>
<content type='text'>
  Empty ${RESOLV_MODS} was causing a deletion of config files in
  /etc/ppp/peers/*

  Resolves: #155
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  Empty ${RESOLV_MODS} was causing a deletion of config files in
  /etc/ppp/peers/*

  Resolves: #155
</pre>
</div>
</content>
</entry>
<entry>
<title>network-functions: use POSIX forwarding instead of bash-ism</title>
<updated>2017-11-09T13:58:51+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2017-11-08T16:25:24+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=cfa035c7c3aeacea60d4e12bebde7ce8e1ecc54b'/>
<id>cfa035c7c3aeacea60d4e12bebde7ce8e1ecc54b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>ifup-post: always update nameserver &amp; search entries in /etc/resolv.conf</title>
<updated>2017-11-02T10:54:44+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2017-10-30T16:08:42+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=4da9dbaffba4af74eb632d1a5d10e5c366475516'/>
<id>4da9dbaffba4af74eb632d1a5d10e5c366475516</id>
<content type='text'>
  This is complete rework of how we generate the /etc/resolv.conf.

  Fixes:
   * always update 'nameserver' &amp; 'search' entries when DNS* &amp; 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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  This is complete rework of how we generate the /etc/resolv.conf.

  Fixes:
   * always update 'nameserver' &amp; 'search' entries when DNS* &amp; 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
</pre>
</div>
</content>
</entry>
<entry>
<title>ifup-eth: wait for STP to complete setup on bridge if $DELAY is not set</title>
<updated>2017-10-31T11:36:19+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2017-07-21T10:13:00+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=75bf420df0f31cc79d1603c2b5a184ccdb151813'/>
<id>75bf420df0f31cc79d1603c2b5a184ccdb151813</id>
<content type='text'>
  Otherwise obtaining IP from DHCP might fail. Based on patch from:
   * Rich Alloway &lt;richard.alloway@roguewave.com&gt; | CentOS BZ #0011138
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  Otherwise obtaining IP from DHCP might fail. Based on patch from:
   * Rich Alloway &lt;richard.alloway@roguewave.com&gt; | CentOS BZ #0011138
</pre>
</div>
</content>
</entry>
</feed>
