"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I'm wondering what kind of support(if any) potato has for NIS+ (NIS
> w/shadow passwd support) I tried playin with NIS+ on slink about a year
> ago and hosed many machines during libc upgrades. because potato is
> glibc2.1, has anyone got a netwo
I am working in a new network operations center that needs to standardize
on a linux distribution, currently it seems to be leaning towards debian
potato as thats what the unix admins want.(either that or mandrake)
I'm wondering what kind of support(if any) potato has for NIS+ (NIS
w/shadow passwd
In article <[EMAIL PROTECTED]>,
Ben Collins <[EMAIL PROTECTED]> wrote:
>On Thu, Sep 30, 1999 at 03:18:26PM +0100, Paul M Sargent wrote:
>> I have the +:: line at the bottom of my passwd file, and all the yp
>> tools work fine (e.g. 'ypmatch pauls passwd' brings up the right response.)
>
>Have
On Thu, Sep 30, 1999 at 05:44:03PM +0100, Paul M Sargent wrote:
> On Thu, Sep 30, 1999 at 12:27:38PM -0400, Ben Collins wrote:
> >
> > Ok, I misunderstood what you were trying to explain. The no password login
> > is an issue with the pam_unix.so (I though you were saying you couldn't
> > login at
On Thu, Sep 30, 1999 at 12:27:38PM -0400, Ben Collins wrote:
>
> Ok, I misunderstood what you were trying to explain. The no password login
> is an issue with the pam_unix.so (I though you were saying you couldn't
> login at all with NIS). I already knew about this, and it will be fixed in
> my ne
On Thu, Sep 30, 1999 at 04:07:01PM +0100, Paul M Sargent wrote:
> > That's incorrect, you can login with a password locally because it then
> > acts like a normal UNIX login. You HAVE to add nis to the nsswitch.conf
> > fields in order to use _any_ programs with NIS. This is not a PAM issue.
>
> O
On Thu, Sep 30, 1999 at 10:43:40AM -0400, Ben Collins wrote:
> On Thu, Sep 30, 1999 at 03:42:14PM +0100, Paul M Sargent wrote:
> > On Thu, Sep 30, 1999 at 10:23:04AM -0400, Ben Collins wrote:
> > > Have you tried adding nis to the /etc/nsswitch.conf fields? Note, than the
> > > pam_unix.so modules
On Thu, Sep 30, 1999 at 03:42:14PM +0100, Paul M Sargent wrote:
> On Thu, Sep 30, 1999 at 10:23:04AM -0400, Ben Collins wrote:
> > Have you tried adding nis to the /etc/nsswitch.conf fields? Note, than the
> > pam_unix.so modules (being that they use standard libc calls for use
> > lookups) recogni
On Thu, Sep 30, 1999 at 10:23:04AM -0400, Ben Collins wrote:
> Have you tried adding nis to the /etc/nsswitch.conf fields? Note, than the
> pam_unix.so modules (being that they use standard libc calls for use
> lookups) recognizes NIS with any problems, so long as the NS Switch is
> setup properly.
On Thu, Sep 30, 1999 at 03:18:26PM +0100, Paul M Sargent wrote:
> I have, what I expect is, a simple problem.
>
> I'm trying to set my Potato box to use NIS to do the lookup for /etc/passwd.
> I have the +:: line at the bottom of my passwd file, and all the yp
> tools work fine (e.g. 'ypmatch
I have, what I expect is, a simple problem.
I'm trying to set my Potato box to use NIS to do the lookup for /etc/passwd.
I have the +:: line at the bottom of my passwd file, and all the yp
tools work fine (e.g. 'ypmatch pauls passwd' brings up the right response.)
I've even got autofs automout
It seems that I potato nis package is still working fine for me.
Chanop
On Sun, Aug 01, 1999 at 01:03:59PM -0700, Alex Romosan wrote:
> Marcin Kurc <[EMAIL PROTECTED]> writes:
>
> > I have upgraded to potato with NIS 3.4-1. Everything worked fine with slink
> > NIS
Marcin Kurc <[EMAIL PROTECTED]> writes:
> I have upgraded to potato with NIS 3.4-1. Everything worked fine with slink
> NIS package but now I cannot connect to NIS master. For example, ypcat passwd
> output:
>
> [EMAIL PROTECTED]:/etc]# ypcat passwd
> yp_all: clnt_call: RPC: Timed out
> No such
I have upgraded to potato with NIS 3.4-1. Everything worked fine with slink NIS
package but now I cannot connect to NIS master. For example, ypcat passwd
output:
[EMAIL PROTECTED]:/etc]# ypcat passwd
yp_all: clnt_call: RPC: Timed out
No such map passwd.byname. Reason: Internal NIS error
Does an
14 matches
Mail list logo