Dear people, I have a problem with udev some weeks ago when I installed a new system using etch. All was ok till I put the box under the ldap server. Then the udev starting script began to doesn't work.
I found a similar problem (yes, I addmit that I didn't read the README.Debian file ... :-( ) in the David Pashley [1] blog. I think that David explain perfectly the problem. I can only add that using a ldap without any wins also fails. The solution he proposed works to me and not the Sergio's because severals reasons: 1) maybe the problem is in the host field, not in pass or group. However, it couldn't work because first put the ldap field and not [UNAVAIL=return] so, it fails in the ldap, as I have tested in my box. 2) probably a better option could be, as David told me in a private mail, put the [UNAVAIL=return] before the ldap, but it doesn't work to me neither. Maybe is something in the pam.d/ files. 3) a perfect solution in to put in the hosts field in the nsswitch.conf file: hosts: files dns [UNAVAIL=return] ldap mdns wins that it works, at least to me. Otherwise, to me, the question is why a program the manages the devices needs when start to create, to check users and groups, when maybe this information is stored in a network device/system, and the udev is the responsible of wake up the interface. I think that this is a dead lock. Regards, Leo [1] http://www.davidpashley.com/cgi/pyblosxom.cgi/debian/nss_wins.html -- Linux User 152692 Catalonia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
