<feed xmlns='http://www.w3.org/2005/Atom'>
<title>initscripts/sysconfig/network-scripts, branch 9.80</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>use proper shebang</title>
<updated>2018-05-17T12:42:21+00:00</updated>
<author>
<name>Matteo Croce</name>
<email>mcroce@redhat.com</email>
</author>
<published>2018-04-09T21:59:22+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=fd269fff7f638b40372fb1cecbf2b74fcb2d079a'/>
<id>fd269fff7f638b40372fb1cecbf2b74fcb2d079a</id>
<content type='text'>
$" is a BASH extension to translate text.
Replace the shebang with /bin/bash to avoid parsing errors,
as even BASH has a POSIX compliant mode when run as sh.

Signed-off-by: Matteo Croce &lt;mcroce@redhat.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
$" is a BASH extension to translate text.
Replace the shebang with /bin/bash to avoid parsing errors,
as even BASH has a POSIX compliant mode when run as sh.

Signed-off-by: Matteo Croce &lt;mcroce@redhat.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>network-functions: use tr to upper case strings rather than awk</title>
<updated>2018-05-17T12:37:21+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=beeec3c4050e2986f514725c92d1cb1d65005926'/>
<id>beeec3c4050e2986f514725c92d1cb1d65005926</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>network-functions: add error messages for bonding installation</title>
<updated>2018-05-17T12:34:09+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=aed9dbbe5c70c973df0691b8d0e3565241120fe0'/>
<id>aed9dbbe5c70c973df0691b8d0e3565241120fe0</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...
</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...
</pre>
</div>
</content>
</entry>
<entry>
<title>ifdown-eth: no longer needed 'pidof -x dhclient' condition removed</title>
<updated>2018-05-17T12:28:50+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=3f178ab90d8b06f0396c9580b7886de1e2a92b49'/>
<id>3f178ab90d8b06f0396c9580b7886de1e2a92b49</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>ifup-tunnel: Support 'external' tunnels (#172)</title>
<updated>2018-03-27T22:47:04+00:00</updated>
<author>
<name>Phil Dibowitz</name>
<email>phil@ipom.com</email>
</author>
<published>2018-03-27T22:47:04+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=a0172c375c724e8d4bfbba1d061e70bcb494bc79'/>
<id>a0172c375c724e8d4bfbba1d061e70bcb494bc79</id>
<content type='text'>
* ifup-tunnel: Support 'external' tunnels

This is a newish feature upstream. You can now set the external flag on a
ip6_tunnel type interface (though not the primary one, ip6tnl0), and doing so
will allow it to decapsulate any packet, and assuming that the inner address is
the one on that interface, it'll drop it back on the stack.

This is useful for DSR vips. While v6-in-v6 was already supported, this allows
v4-in-v6 which is necessary to serve v4 traffic in a v6only infrastructure.

There's comments in ifup-tunnel that imply it was designed only for GRE tunnels,
but this still seems like the best place for this.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* ifup-tunnel: Support 'external' tunnels

This is a newish feature upstream. You can now set the external flag on a
ip6_tunnel type interface (though not the primary one, ip6tnl0), and doing so
will allow it to decapsulate any packet, and assuming that the inner address is
the one on that interface, it'll drop it back on the stack.

This is useful for DSR vips. While v6-in-v6 was already supported, this allows
v4-in-v6 which is necessary to serve v4 traffic in a v6only infrastructure.

There's comments in ifup-tunnel that imply it was designed only for GRE tunnels,
but this still seems like the best place for this.</pre>
</div>
</content>
</entry>
<entry>
<title>ifdown-post: fix logical error in commit 5d61564</title>
<updated>2018-01-02T15:02: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=0f74b85d7d6dd96ce230950b258c9c6e1cf25335'/>
<id>0f74b85d7d6dd96ce230950b258c9c6e1cf25335</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-09T10:19:14+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=2343075df4b18b5fbd35d2fe5f99f16e59478b3c'/>
<id>2343075df4b18b5fbd35d2fe5f99f16e59478b3c</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-10-31T12:11:59+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=5d6156454bf8f6dab4a5fdd7e1bf6cdc72c09456'/>
<id>5d6156454bf8f6dab4a5fdd7e1bf6cdc72c09456</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
   * always keep /etc/resolv.conf.save as a proper backup - do not
     overwrite it everytime when updating 'nameserver' or 'search'

  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
   * always keep /etc/resolv.conf.save as a proper backup - do not
     overwrite it everytime when updating 'nameserver' or 'search'

  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>network-scripts: forward DBus calls to /dev/null</title>
<updated>2017-10-31T11:16:43+00:00</updated>
<author>
<name>David Kaspar [Dee'Kej]</name>
<email>dkaspar@redhat.com</email>
</author>
<published>2017-10-31T11:14:30+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=9e48c7ad6fae91a333d0b0a39cffee14a3130f2c'/>
<id>9e48c7ad6fae91a333d0b0a39cffee14a3130f2c</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Spelling fixes</title>
<updated>2017-10-30T16:06:33+00:00</updated>
<author>
<name>Ville Skyttä</name>
<email>ville.skytta@iki.fi</email>
</author>
<published>2017-10-23T20:08:12+00:00</published>
<link rel='alternate' type='text/html' href='https://gitweb.mageia.org/software/forks/initscripts/commit/?id=ee33104d73ae642b1507957a424226b03ea43da6'/>
<id>ee33104d73ae642b1507957a424226b03ea43da6</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
