aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ifup-eth: Fix bridge setting stp optionBell2019-08-211-1/+1
| | | | | | | | | | | Fixes https://bugzilla.redhat.com/1743522 An uninitialized variable was copied from a closed PR [1] to submitted PR [2]. [1] https://github.com/fedora-sysv/initscripts/pull/212 [2] https://github.com/fedora-sysv/initscripts/pull/213 Signed-off-by: Bell Levin <blevin@redhat.com>
* Fix bug in service(8)Jan Macku2019-08-211-1/+1
|
* ifup-eth: Check that device name is setJan Macku2019-08-191-0/+5
|
* Fix missing python3 during build phaseJan Macku2019-08-123-3/+7
|
* rc.d/functions: fix escape sequence being output under systemd service unitsHATAYAMA Daisuke2019-08-071-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When functions provided by /etc/rc.d/functions is used, escape sequence is output under systemd service units and logged into /var/log/messages as follows: # LANG=C systemctl cat foobar.service # /etc/systemd/system/foobar.service [Unit] Description=FOOBAR [Service] Type=oneshot ExecStart=/usr/bin/foobar.sh RemainAfterExit=yes [Install] WantedBy=multi-user.target # cat /usr/bin/foobar.sh #! /bin/bash . /etc/init.d/functions echo_success # LANG=C grep foobar.sh /var/log/messages Aug 7 09:29:54 localhost foobar.sh[29607]: #033[60G[#033[1;32m OK #033[0;39m]#015#033[60G[#033[1;31mFAILED#033[0;39m] This is a regression issue caused by the commit f88dbd98e992 where consoletype command was dropped. Under systemd service units, standard input is associated with /dev/null by default: # systemctl show -p StandardInput foobar.service StandardInput=null man 5 systemd.exec: StandardInput= Controls where file descriptor 0 (STDIN) of the executed processes is connected to. Takes one of null, tty, tty-force, tty-fail, data, file:path, socket or fd:name. If null is selected, standard input will be connected to /dev/null, i.e. all read attempts by the process will result in immediate EOF. consoletype command interprets /dev/null as serial: # consoletype < /dev/null warning: consoletype is now deprecated, and will be removed in the near future! warning: use tty (1) instead! More info: 'man 1 tty' serial The commit f88dbd98e992 overlooks this situation. To fix this issue, check also "not a tty" to cover the case where standard input is /dev/null. Note that LANG=C is needed because the message "not a tty" varies depending on locales.
* Add ip6gre tunnel optionJan Macku2019-07-313-2/+7
| | | | Resolve: BZ #1691552
* ifup/ifdown: print DEPRECATION_WARNING_ISSUED waring info after source_configZhiqiang Liu2019-07-252-12/+12
| | | | | | | | | In ifup/ifdown scripts, move deprecation waring info after source_config, so users can config DEPRECATION_WARNING_ISSUED in ifcfg-** file to decide whether show deprecation waring info when calling ifup/ifdown. Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
* 10.0210.02Jan Macku2019-06-281-1/+11
|
* network: don't fail with IFDOWN_ON_SHUTDOWNLukas Nykryn2019-06-101-2/+2
|
* rc.d/functions: remove support cgroupsLukas Nykryn2019-06-062-23/+2
| | | | | Now with systemd, this does not work pretty well and users really should use systemd unit-files for this.
* Create symlink (/etc/init.d) to /etc/rc.d/init.dJan Macku2019-06-062-0/+3
| | | | Resolve problem when wasn't installed chkconfig package. BZ #1716386
* Add option to wait until target is reachableJan Macku2019-04-042-1/+23
| | | | | | | | | | | | | | | | | | Add option for time saving waiting Replace date with simple timeout Rename configurable variable and add documentation Print log only when didn't reach IP address in time Add support for IPv6 address Remove unneeded output Change -ge to -gt, because equal value is ok Clarify DNS name option in documentation
* ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemonZhiqiang Liu2019-02-121-1/+7
| | | | | | | | | | | | | | | | | | | IPv6 dhclient daemon only tries one time to obtain a IPv6 address from a DHCPv6 server regardless of the setting of PERSISTENT_DHCLIENT. PERSISTENT_DHCLIENT option is only used for IPv4 dhclient daemon. With the popularization of IPv6 protocol, some users prefer setting IPv6 like IPv4. I think there are two solutions as follows, 1. adopt PERSISTENT_DHCLIENT option to both IPv4 and IPv6. 2. create a new option, such as PERSISTENT_DHCLIENT_IPV6 option, just for IPv6. The first solution does not introduce addition options, and the IPv4 and IPv6 settings are consistent. So I perfer choosing the first solution. Fixes: bf00a0048 ("Replace /var/run with /run everywhere") Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
* ifup-post: fix incorrect condition for RESOLV_MODSDavid Kaspar [Dee'Kej]2018-08-241-1/+1
| | | | | | | | | | 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.
* make tag: updated messageDavid Kaspar [Dee'Kej]2018-08-071-1/+1
| | | | | GitHub displays the tag message when we create new release there, so lets have message with more sense...
* make release-commit: do not create tag automaticallyDavid Kaspar [Dee'Kej]2018-08-071-1/+0
| | | | | | | | GitHub will create a new commit with different hash (merge) when applying the pull-request, and so the tag ended up pointing to wrong commit hash... For now we have to tag the release commits manually.
* 10.0110.01David Kaspar [Dee'Kej]2018-08-061-1/+7
|
* network/ifup/ifdown: deprecations warnings redirected to stderrDavid Kaspar [Dee'Kej]2018-08-063-9/+9
|
* ifup-eth: use 'bc' instead of 'expr' when computing $forward_delayDavid Kaspar [Dee'Kej]2018-08-032-2/+5
| | | | | | | | | | | | | | | | Because the return value of 'convert2sec()' function can sometimes be decimal, the follow up 'expr' call can fail, since 'expr' does not support floating point calculations. This can sometimes lead to error: """ expr: non-integer argument /etc/sysconfig/network-scripts/ifup-eth: line 91: [: 0: unary operator expected """ To solve this bug, we switch to 'bc' utility, which supports floating point computations. We also have to change the comparison condition of $LINKDELAY and $forward_delay to use 'bc' as well.
* network/ifup/ifdown: deprecation warnings for 'network-scripts' addedDavid Kaspar [Dee'Kej]2018-08-023-0/+19
| | | | | In case of 'network' service these warnings are displayed only once, to not spam unnecessarily user's journalctl if they have many NICs.
* network: parsing of /proc/mounts returnedDavid Kaspar [Dee'Kej]2018-07-241-1/+6
| | | | | | | 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'.
* 10.0010.00David Kaspar [Dee'Kej]2018-06-211-1/+5
|
* Move the /etc/rwtab.d & /etc/statetab.d folders to 'filesystem'David Kaspar [Dee'Kej]2018-06-212-4/+0
| | | | | | This will allow services to install drop-in files into these folders for the 'readonly-root' service, but that service won't have to be installed by default as a result...
* specfile: fix failing build because of incorrect use of %{_isa}David Kaspar [Dee'Kej]2018-06-151-2/+2
|
* 9.839.83David Kaspar [Dee'Kej]2018-06-141-1/+30
|
* network-scripts: Add previously dropped error checkingPhil Sutter2018-06-141-2/+2
| | | | | When converting from brctl to ip-link, the call to exit in case bridge adding failed was dropped by accident.
* network-scripts: Replace brctl with ip-linkPhil Sutter2018-06-142-17/+19
| | | | | Since ip-link has full support for Linux bridges (and slave ports), use that instead of the deprecated brctl from bridge-utils.
* Makefile: new release-commit rule addedDavid Kaspar [Dee'Kej]2018-06-141-3/+13
|
* src/rename_device.c: GCC warnings about unused return value suppressedDavid Kaspar [Dee'Kej]2018-06-141-2/+3
|
* src/usernetctl.c: GCC warnings about unused return value suppressedDavid Kaspar [Dee'Kej]2018-06-141-2/+3
|
* Makefile: allow sub-makefiles to run in parallelDavid Kaspar [Dee'Kej]2018-06-141-7/+7
|
* specfile: netconsole service moved to /usr/libexecDavid Kaspar [Dee'Kej]2018-06-143-5/+22
|
* specfile: services from /usr/lib/systemd moved to /usr/libexecDavid Kaspar [Dee'Kej]2018-06-149-14/+15
|
* specfile: summary & description updatedDavid Kaspar [Dee'Kej]2018-06-141-3/+3
|
* specfile: no longer needed conflicts droppedDavid Kaspar [Dee'Kej]2018-06-141-8/+0
|
* specfile: requirements cleanupDavid Kaspar [Dee'Kej]2018-06-141-21/+16
|
* specfile: obsoletes on previous version of initscripts package addedDavid Kaspar [Dee'Kej]2018-06-141-0/+8
| | | | | | | | This makes sure all the subpackages stay installed during the upgrade for Fedora users. After that users will be able to manually remove the packages if needed... Fresh installations will have only initscripts installed.
* specfile: network-scripts subpackage createdDavid Kaspar [Dee'Kej]2018-06-1410-28/+78
|
* specfile: readonly-root subpackage createdDavid Kaspar [Dee'Kej]2018-06-141-15/+55
|
* specfile: netconsole-service subpackage createdDavid Kaspar [Dee'Kej]2018-06-141-4/+38
|
* README.md: Travis CI build icon addedDavid Kaspar [Dee'Kej]2018-06-131-1/+1
|
* .travis.yml: check the 'make install' proceeds as wellDavid Kaspar [Dee'Kej]2018-06-131-1/+1
|
* .travis.yml: initial commitDavid Kaspar [Dee'Kej]2018-06-131-0/+12
| | | | To build in container-based environment because of speed.
* README.md: bug reporting describedDavid Kaspar [Dee'Kej]2018-06-121-0/+10
|
* README.dm: future of initscripts describedDavid Kaspar [Dee'Kej]2018-06-121-0/+15
|
* README.md: description addedDavid Kaspar [Dee'Kej]2018-06-121-0/+20
|
* README.md: references to old git branches addedDavid Kaspar [Dee'Kej]2018-06-121-0/+45
|
* README.md: initial commitDavid Kaspar [Dee'Kej]2018-06-121-0/+7
| | | | Resolves: #75
* network-scripts: setting of firewall ZONE fixedDavid Kaspar [Dee'Kej]2018-06-073-5/+6
| | | | | | | | | | | | | 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
* ifdown-post: artifact whitespace removed from the DBus callDavid Kaspar [Dee'Kej]2018-06-071-1/+1
| | | | | | | This was causing the DBus call to fail, and we didn't catch it before since we were forwarding everything into /dev/null... Related: RHBZ#1586284
generated by cgit v1.2.1 (git 2.21.0) at 2024-11-24 14:45:00 +0000