Bug 38
Summary: | 'cd /etc/rc.d/init.d/; network restart' doesn't work | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | redhat-bugzilla |
Component: | initscripts | Assignee: | David Lawrence <dkl> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-05-17 14:01:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
redhat-bugzilla
1998-11-11 11:54:29 UTC
More information needed; the bug report is mostly confusing. What exactly it is failing and how can one reproduce it? The problem report is that "network restart" won't work if it is invoked with a relative path. `/etc/rc.d/init.d/network restart' will work, 'cd /etc/rc.d/init.d; network restart' won't, and neither will 'cd /etc/rc.d; ./init.d/network restart'. The reference to 'linuxconf' points out that 'network reload' suffers from the same bug when there is no 'linuxconf'. This isn't much of a loss IMHO, although trying to re-invoke your own executable in general is very bad style. If we really wanted this to work, we'd define shell functions within the 'network' script and then call them: netstop () { # blah blah blah } netstart () { # blah blah blah } case "$1" in start) netstart ;; stop) netstop ;; restart) netstop netstart ;; esac fixed |