From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Cc: "Enils Bashi" <EBashi@chesapeakebay.net>
Subject: Re: ypxfr: Can't get master address
Date: Fri, 30 Jul 2004 15:14:57 +0200 [thread overview]
Message-ID: <200407301515.00932.bernd-schubert@web.de> (raw)
In-Reply-To: <C9D51E2209AFD04F93E4E2E4CD6E497925924D@mail1.chesapeakebay.net>
> I am looking at my /var/log/messages on Redhat Linux 9 running ypserv
> 2.8 and here is what I see on the NIS master:
>
> Jul 30 08:00:00 <myserver> ypxfr[22647]: ypxfr: Can't get master address
> Jul 30 08:00:00 <myserver> ypserv[1505]: refused connect from
> 127.0.0.1:776 to procedure ypproc_master (linux-nis,publickey.byname;-4)
>
> Also lately our linux users have been complaining about passwords
> changes not being propagated to the nis slaves and client. I wonder
> whether these errors have anything to do with it.
>
> Any and all feedback would be greatly appreciated...
>
Well, thats a NIS problem, but this is a NFS mailing list.
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-07-30 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 12:29 ypxfr: Can't get master address Enils Bashi
2004-07-30 13:14 ` Bernd Schubert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407301515.00932.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=EBashi@chesapeakebay.net \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.