Once you make the network interface no longer NM managed you can then perform
a service network restart in your post and all network functionality should
then become available.
This may be desired or true in theory, but is not working.
I have NM_CONTROLLED=no in ifcfg-eth0, and it works
Lars Hecking wrote:
Once you make the network interface no longer NM managed you can then
perform a service network restart in your post and all network
functionality should then become available.
This may be desired or true in theory, but is not working.
I have NM_CONTROLLED=no in
| Won't help in this case, I think, as this behaviour already makes my
| kickstart
| %post fail.
Correcting myself ... what fails is an init script generated at %post time.
Once you make the network interface no longer NM managed you can then perform
a service network restart in your
- Original Message -
|
| | The other machine doesn't have NetworkManager installed. Removed
| | it
| | here
| | and NIS/autofs started working correctly.
|
| You don't have to remove NetworkManager you just need to tell the
| interface not to be managed by NM in order for it
| The other machine doesn't have NetworkManager installed. Removed it
| here
| and NIS/autofs started working correctly.
You don't have to remove NetworkManager you just need to tell the interface
not to be managed by NM in order for it to work.
Won't help in this case, I think, as
Lars Hecking writes:
Lars Hecking writes:
One problem I have with custom CentOS 6 installation is that NIS auto.*
maps are not available. According to boot.log, ypbind starts before autofs,
but when I login to the machine, the maps are not available until I issue
a service autofs
- Original Message -
| Lars Hecking writes:
| Lars Hecking writes:
|
|One problem I have with custom CentOS 6 installation is that NIS
|auto.*
|maps are not available. According to boot.log, ypbind starts
|before autofs,
|but when I login to the machine, the maps
One problem I have with custom CentOS 6 installation is that NIS auto.*
maps are not available. According to boot.log, ypbind starts before autofs,
but when I login to the machine, the maps are not available until I issue
a service autofs restart.
Any pointers on what to check?
Lars Hecking writes:
One problem I have with custom CentOS 6 installation is that NIS auto.*
maps are not available. According to boot.log, ypbind starts before autofs,
but when I login to the machine, the maps are not available until I issue
a service autofs restart.
Any pointers on
9 matches
Mail list logo
