From bb@suse.com Mon Mar 2 21:05:50 1998
From: bb@suse.com
To: users@lists.opensuse.org
Subject: Re: [S.u.S.E. Linux] NIS Server
Date: Mon, 02 Mar 1998 22:05:50 +0100
Message-ID: <6df6ve$h47$1@Galois.suse.de>
In-Reply-To: <[S.u.S.E. Linux] NIS Server>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4428337460665032620=="
--===============4428337460665032620==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mario Oschwald wrote:
>=20
> Steven 'Svet' Downum wrote:
>=20
> > Hey everyone,
> >
> > I'm having trouble setting up a NIS server on SuSE Linux
> > 5.1...I've been using the NIS HowTO and the yp commands in O'Reilly's
> > Linux in a Nutshell. Both refer to a ypinit command I cannot find. I found
> > a ypmake command that which sounds like it should do what ypinit does,
> > make the map databases. Has anyone got an NIS server up on 5.1 and, if so,
> > how?
> >
> >
>=20
> First you have to decide if you want to run your machine as master or slave
> NIS server.If there=C5=BDs already a machine in your net running as master =
server
> you should install your machine
> as slave server. Use YaST to start the ypserver, portmapper and also the
> yppasswdd (to enable remote changing
> of passwords). Also make sure that your server is also configured as a
> client, it should bind to itself.
> Check if the demons are running with rpcinfo -p localhost. You should have
> the portmapper,ypbind,
> ypserv and yppasswd running. ypinit should be found in /usr/lib/yp use ypin=
it
> -m or ypinit -s masterserver to create the ypdatabases or get them from the
> master. remember that this directory
> is usually not in your path so use the full path to run ypinit. also make
> sure that your master server
> knows about your machine if you install it as slave server, so it
> automatically sends you updated
> versions of its databases. ypmake can be used on a masterserver to update
> single databases.
> use ypwhich (who=C5=BDs server) ypcat (what=C5=BDs in the database) command=
s to check
> your connections.
There is a bug in the S.u.S.E. init scripts for setting up an NIS server.
The ypdomainname is not set in the ypserv startscript, and the server
is started after the client. So you have to include a line like
domainname $YP_DOMAINNAME
in /sbin/init.d/ypserv and switch the links in /sbin/init.d/rc[23].d to
lrwxrwxrwx 1 root root 11 Jan 22 18:00 rc2.d/K25ypclient -> .=
./ypclient
lrwxrwxrwx 1 root root 12 Jan 22 18:00 rc2.d/K25yppasswdd -> =
../yppasswdd
lrwxrwxrwx 1 root root 9 Jan 22 18:00 rc2.d/K25ypserv -> ../=
ypserv
lrwxrwxrwx 1 root root 9 Dec 16 06:53 rc2.d/S14ypserv -> ../=
ypserv
lrwxrwxrwx 1 root root 11 Jan 22 18:00 rc2.d/S15ypclient -> .=
./ypclient
lrwxrwxrwx 1 root root 12 Jan 22 18:00 rc2.d/S15yppasswdd -> =
../yppasswdd
Ciao,
BB
--=20
Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873=20
bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875
http://www=
.suse.com> Oakland CA, 94610 USA
--
To get out of this list, please send email to majordomo(a)suse.com with
this text in its body: unsubscribe suse-linux-e
--===============4428337460665032620==--