Re: NIS Problem ... about to be solved? (I hope)
At 05:28 PM 11/06/97 -0400, Pedro I. Sanchez wrote: Hello, A few days ago I reported the problem of NIS not working in Debian 1.3. It still does not work and unfortunately no one seems to have an answer. However, I just read the following from H.J. Lu regarding his new release (5.4.33) of libc: Yes, I do agree with you that Debian 1.3 broke NIS - but not the latest version of disks. I decided to test the latest disk set 1997-05-30 (I can't remember the date of the last 1.3 disks) and NIS now works for me - you must make sure you say No to shadow passwords during the setup as well (I think it defaults to yes if you press enter). Regards -- Karl Ferguson, Tower Networking Pty LtdTel: +61 8 9456 [EMAIL PROTECTED] t/a STAR Online ServicesFax: +61 8 9455 2776[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: NIS Problem ... about to be solved? (I hope)
On Thu, 12 Jun 1997, Karl Ferguson wrote: At 05:28 PM 11/06/97 -0400, Pedro I. Sanchez wrote: Hello, A few days ago I reported the problem of NIS not working in Debian 1.3. It still does not work and unfortunately no one seems to have an answer. However, I just read the following from H.J. Lu regarding his new release (5.4.33) of libc: Yes, I do agree with you that Debian 1.3 broke NIS - but not the latest version of disks. I decided to test the latest disk set 1997-05-30 (I can't remember the date of the last 1.3 disks) and NIS now works for me - you must make sure you say No to shadow passwords during the setup as well (I think it defaults to yes if you press enter). My servers went from Debian 1.1 to 1.2 to 1.3 using ftp to upgrade. The last time I used the installations diskettes was when I installed 1.1. During this process I don't recall having been asked for any shadow options at all. Can you tell me what package is suppose to ask something about shadow passwords? Even more, can someone explain how shadow passwords relate to the NIS stuff? Probably here is where I have my problems. Thank you, -- Pedro I. Sanchez -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: NIS Problem ... about to be solved? (I hope)
At 09:57 AM 12/06/97 -0400, Pedro I. Sanchez wrote: My servers went from Debian 1.1 to 1.2 to 1.3 using ftp to upgrade. The last time I used the installations diskettes was when I installed 1.1. During this process I don't recall having been asked for any shadow options at all. Can you tell me what package is suppose to ask something about shadow passwords? Even more, can someone explain how shadow passwords relate to the NIS stuff? Probably here is where I have my problems. Well this won't affect you then - I was referring to a completely fresh install of the 1.3 basedisks - during that setup it asks whether or not you want to uyse shadow passwords. Enabling shadow passwords in 1.3 is simply a matter of doing a shadowconfig on at the prompt - however, I advise not to do it, it may break NIS. Basically, to find if your running a shadow system, see if you've got the /etc/shadow file with all your passwords in it or not. Regards -- Karl Ferguson Tower Networking Pty Ltd Tel: +61-8-9456- [EMAIL PROTECTED] t/a STAR Online Services Fax: +61-8-9455-2776 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: NIS Problem ... about to be solved? (I hope)
Karl Ferguson wrote: Well this won't affect you then - I was referring to a completely fresh install of the 1.3 basedisks - during that setup it asks whether or not you want to uyse shadow passwords. Enabling shadow passwords in 1.3 is simply a matter of doing a shadowconfig on at the prompt - however, I advise not to do it, it may break NIS. Basically, to find if your running a shadow system, see if you've got the /etc/shadow file with all your passwords in it or not. Regards I don't have any /etc/shadow file on my systems. So, I'm back to nothing. My only hope is that the new libc is released soon and will solve my problem. By the way, will it be released to the stable tree? -- Pedro I. Sanchez -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
NIS Problem ... about to be solved? (I hope)
Hello, A few days ago I reported the problem of NIS not working in Debian 1.3. It still does not work and unfortunately no one seems to have an answer. However, I just read the following from H.J. Lu regarding his new release (5.4.33) of libc: ... 4. I have modified the NIS support in libc, which is not compatible with the previous version, but is compatible with SunOS, Solaris, ... except for those brain dead xxxBSD. Please make sure you have the same ypclients as the one at where you get this C library. Otherwise your NIS won't work with the modified NIS code in this libc. If you use a different yp client other than those in my YP clients package, you may need a patch. Please send me a note and I will fix it for you as soon as possible. Now, Does debian uses Lu's YP client package. Could it be that the source of the NIS problems is a mismatch between Debian's YP clients/servers and libc libraries? Could this new libc release solve the problems? I whish someone could elaborate a bit more on this issue. Just in case someone who might help me with the NIS problem is reading about it by the first time in this list, I explain what is happening to me after my signature. Thank you, -- Pedro I. Sanchez Here is what happens to me. I have two Debian 1.3 boxes. One runs the NIS server, the other is a client. What follows is a transcript of a two-command session in the client machine: ~ypmatch rover passwd rover:V/8DB9sycYRnM:1017:1017:Nadia Rover:/home/rover:/bin/bash ~su rover su: user rover does not exist all other YP commands work well like ~ypcat -x Use passwd for passwd.byname Use group for group.byname Use networks for networks.byaddr Use hosts for hosts.byname Use protocols for protocols.bynumber Use services for services.byname Use aliases for mail.aliases Use ethers for ethers.byname and no errors are reported anyplace. So, the ypbind client connects with the server but for some reason the system commands, like su or ls, cannot see the NIS mappings. I am running libc5_5.4.23-6, libc6_2.0.3-4 and NIS_2.20-1. I have a third Debain box on the works and three more are about to come. However, if this problem is not solved soon, I'm afraid I'll be forced to completely replace Debian with Solaris. I wish someone could help. I really enjoy Debian. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
