FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 02-10-2012, 03:30 PM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

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?

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-10-2012, 03:47 PM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

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 what to check?

I guess CentOS doesn't use pid randomisation. autofs does start before
ybind:

root 2107 1 0 16:40 ? 00:00:00 automount --pid-file /var/run/autofs.pid
root 2517 1 0 16:41 ? 00:00:00 /usr/sbin/ypbind
root 3009 2976 0 16:43 pts/0 00:00:00 egrep auto|ypb

Another machine I installed interactively (this one is kickstarted) works
correctly.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-13-2012, 12:00 PM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

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 restart.
> >
> > Any pointers on what to check?
>
> I guess CentOS doesn't use pid randomisation. autofs does start before
> ybind:
>
> root 2107 1 0 16:40 ? 00:00:00 automount --pid-file /var/run/autofs.pid
> root 2517 1 0 16:41 ? 00:00:00 /usr/sbin/ypbind
> root 3009 2976 0 16:43 pts/0 00:00:00 egrep auto|ypb
>
> Another machine I installed interactively (this one is kickstarted) works
> correctly.

Solved.

The other machine doesn't have NetworkManager installed. Removed it here
and NIS/autofs started working correctly.

Why again did RH switch to NM?

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-13-2012, 07:16 PM
"James A. Peltier"
 
Default init/upstart issue? ypbind and 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 are not available
| > > until I issue
| > > a service autofs restart.
| > >
| > > Any pointers on what to check?
| >
| > I guess CentOS doesn't use pid randomisation. autofs does start
| > before
| > ybind:
| >
| > root 2107 1 0 16:40 ? 00:00:00 automount
| > --pid-file /var/run/autofs.pid
| > root 2517 1 0 16:41 ? 00:00:00 /usr/sbin/ypbind
| > root 3009 2976 0 16:43 pts/0 00:00:00 egrep auto|ypb
| >
| > Another machine I installed interactively (this one is
| > kickstarted) works
| > correctly.
|
| Solved.
|
| 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.


| Why again did RH switch to NM?

To better support mobile devices like laptops and to make network configuration easier for new GNU/Linux users.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-14-2012, 09:03 AM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

> | 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 this behaviour already makes my kickstart
%post fail.

> | Why again did RH switch to NM?
>
> To better support mobile devices like laptops and to make network configuration easier for new GNU/Linux users.

Well, I appreciate NM on laptops, but this is a distro geared towards
enterprise. I can't imagine many enterprise users running a distro on
laptops where most software components are already outdated upon release
and support for newer hw may be sketchy.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-15-2012, 04:37 PM
"James A. Peltier"
 
Default init/upstart issue? ypbind and autofs

----- 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 to work.
|
| Won't help in this case, I think, as this behaviour already makes my
| kickstart
| %post fail.

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.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 02-17-2012, 01:47 PM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

> | 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 post and all network functionality should
> then become available.

I don't see the need for NM on racked servers and stationary workstations.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 03-12-2012, 03:05 PM
Lars Hecking
 
Default init/upstart issue? ypbind and autofs

> 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 according to the logs
("Ignoring connection 'System eth0' and its device due to NM_CONTROLLED/BRIDGE/VLAN"),
but NIS is not working. yp.conf is correct as created through dhcp,
domainname returns the correct domain, and ypbind is running. Yet ypwhich
returns cannot communicate with ypbind. Once I stop NetworkManager, it
starts working.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 03-12-2012, 04:14 PM
 
Default init/upstart issue? ypbind and autofs

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 ifcfg-eth0, and it works according to the
> logs
> ("Ignoring connection 'System eth0' and its device due to
> NM_CONTROLLED/BRIDGE/VLAN"),
> but NIS is not working. yp.conf is correct as created through dhcp,
> domainname returns the correct domain, and ypbind is running. Yet ypwhich
> returns cannot communicate with ypbind. Once I stop NetworkManager, it
> starts working.

Yeah. Here, we do chkconfig NetworkManager off, and stop it. Then we have
a lot fewer issues.

mark

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 09:53 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org