Re: configuration of nsswitch.conf ignored by system
Hi Thomas, On Mo, 2004-08-23 at 18:59 +0200, Thomas Hood wrote: I've the problem that on all debian systems (Woody, Sid) it seems that some configuration changes of the nsswitch.conf are ignored by the system. See #160596 and those merged with it. As I am not the over-geek I have to bother you with some further questions: - I read that right that its not a nscd-bug or something but a bug in the glibc which doesnt handle the nsswitch.conf the correct way? - The bug was tagged WONTFIX...does this just mean that nobody from the Deb-Crew will fix it because it relies on other developers? - Where can I monitor this bug, where will I see when the bug is fixed as this is really a pain in the ass on one of our production systems. - Does anybody know the timeframe in which such a bug will be fixed? Days, Months, Years? Because the original Bug opener is from 2002! Thanks, Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuration of nsswitch.conf ignored by system
Hi On Di, 2004-08-24 at 09:47 +0200, Thomas Hood wrote: The Debian maintainers seem to regard it as a feature of glibc rather than as a bug. [...] They regard it as a feature, so the behavior probably will not be changed. How can it be a feature when I make some configuration to nsswitch.conf (meaning: dear lookup-process, please stop here when successfull) and this is ignored? If a configuration is ignored it should be (nearly) always a bug, shouldnt it? ;-) It won't be fixed. There is a workaround, though, involving the addition of IPv6 lines to /etc/hosts. Read through all the reports carefully to get a full picture. Ok, maybe we come closer, maybe the bug you told me is not the one which fits to my problem, because I do not have any problems with the hosts-lookup, but with the groups-lookup! So it shouldnt have to something with getaddrinfo, should it? Thanks, Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuration of nsswitch.conf ignored by system
On Tue, 2004-08-24 at 09:43, Matthias Eichler wrote: - I read that right that its not a nscd-bug or something but a bug in the glibc which doesnt handle the nsswitch.conf the correct way? The Debian maintainers seem to regard it as a feature of glibc rather than as a bug. - The bug was tagged WONTFIX...does this just mean that nobody from the Deb-Crew will fix it because it relies on other developers? They regard it as a feature, so the behavior probably will not be changed. - Where can I monitor this bug, where will I see when the bug is fixed as this is really a pain in the ass on one of our production systems. It won't be fixed. There is a workaround, though, involving the addition of IPv6 lines to /etc/hosts. Read through all the reports carefully to get a full picture. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
configuration of nsswitch.conf ignored by system
Dear DebUsers, I've the problem that on all debian systems (Woody, Sid) it seems that some configuration changes of the nsswitch.conf are ignored by the system. We've a lot of Laptop systems that should resolve the groups also from LDAP - but only as long as they are in our company network. As soon as they leave this network (and can't contact the LDAP server) I've the problem that all logins and all actions where some user- or group-resolving is done take up to minutes (tcp timeout?). For this I've created the following nsswitch.conf: ---cut--- # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc Name Service Switch' for information about this file. passwd: files group: files [SUCCESS=return] ldap #group: files shadow: files hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis ---cut--- For me this config tells that first the process has to look at the local files and when the entry is found the resolving stops and does not start an ldap lookup. Unfortunately this does not work! As long as the ldap entry is in the nsswitch.conf and I cant reach the server I cant work with my system, I have to comment out the ldap-line and have to comment in the files-only-line. == Is this behaviour wanted? == How can I configure my system that it will JUST look into the LDAP when the files-lookup was not successful? Thanks for any help, Matthias P.S.: The problem is that on a server of our company this same bug brings some software to segfault and usually this bug is solved with a config like above, which works not on Debian...:-( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuration of nsswitch.conf ignored by system
I've the problem that on all debian systems (Woody, Sid) it seems that some configuration changes of the nsswitch.conf are ignored by the system. See #160596 and those merged with it. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
