Nick Chalk wrote:
> For the benefit of others who might try this,
> here's a little problem I hit today...
>
> The scenario: Four new Ubuntu Edgy boxes on
> Jamie's Learning Zone network, intended to
> supplement the existing XP machines. I was setting
> them up to fetch account details from the central
> LDAP server, and NFS-mount /home.
>
> Everything was working fine, nss-ldap and pam-ldap
> configured, /home mounted, no problems. Then I
> rebooted...
>
> udevd started complaining that it couldn't see the
> LDAP server. Even booting into single user, it
> took several tens of minutes to get a root prompt.
>
> The problem? Edgy's boot sequence starts udevd
> before loading modules or configuring the network.
> The default order in /etc/rcS.d is...
>
> ...
> S10udevd
> ...
> S15module-init-tools
> ...
> S40networking
> ...
>
> udevd tries to use nss, but can't contact the LDAP
> server because the network isn't up.
>
> A working arrangement, assuming a network driver
> needs to be loaded, is...
>
> ...
> S09module-init-tools
> S10networking
> S11udev
> ...
>
>
> All of which meant that getting these four
> machines working took a /little/ longer than
> planned. :-/
>
> Nick.
>
Oh, this is the point I'm at !!!
Do you have a nice "HowTo" on how to setup a Ubuntu box to authenticate etc again a OpenLDAP box
with home directories exported via NFS ??
Thanks
Brian
------------------------------------------------------------------------
The views expressed here are my own and not necessarily
the views of Portsmouth College
