Red Hat Bugzilla – Bug 426520
This version of ISC DHCP is based on the release available on ftp.isc.org.
Last modified: 2014-03-16 23:11:51 EDT
I have five aliases for eth0 and when I run the command:
service network restart
I get the following message:
[root@penguin ~]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0...dhclient(23988) is already running - exiting.
This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site:
The reason for running the command is because I want the aliases to start also.
When the computer boots up only the parent eth0 starts, the aliases are all
I will attach configuration for eth0 and eth0:1 and eth0:2
When I use the GUI to start the aliases manually it works but no other way works.
Created attachment 290255 [details]
ifcfg-eth0, ifcfg-eth0:1, ifcfg-eth0:2
> The reason for running the command is because I want the aliases to start also.
Then set 'ONPARENT=yes'; that should accomplish this.
Thanks Bill. Sorry, I should have said that I had already tried that option and
it did not work either.
Interesting - the aliases aren't brought up at all?
Quite interesting!! They are not brought up at all. I usually have to use the
settings I attached originally and then once I reboot and the parent device
comes up, I use the GUI Network Configuration tool to bring up the aliases. And
since I do not know yet how to do this from the command line, I cannot do it
while logged through SSH - from another machine.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
I can reproduce this bug in Fedora 12.
its giving error when i try to start my network service.
Reopen Bug !