[ The mail I sent cause error (missing a "Subject" header)
though I had a "Subject:" line in header. So, this is 2nd post.]
Hi Gyula,
Thank you very much for your responding.
szgyula_at_skysrv.Pha.Jhu.EDU (Mon, 17 Jun 1996 22:00:18 -0400) writes:
> > How can I add a new NIS database on DigitalUnix ?
>
> Well, I have a Solaris 2.x YP master, and an OSF/1 v3.0 slave (replica).
> Client include: SunOS 4.x, Solaris 2.x, OSF/1 3.0, DUnix 3.2, 4.0.
> /etc/svc.conf have:
>
> aliases=local,yp
> group=local,yp
> hosts=local,bind,yp
> netgroup=yp
> networks=local
> passwd=local,yp
> protocols=local
> rpc=local
> services=local
>
> SECLEVEL=BSD # for backwards compatibility ONLY
>
> In /etc/passwd I have lines like:
>
> +tunison
> +rosati
>
> (just like with good old SunOS).
> I have one minor problem, which is not critical, so I never looked into
> it. When I do a 'make' on the master, it just sits there forever.
> All this was created by nissetup.
Oh, you have SECLEVEL=BSD in /etc/svc.conf .
May I ask what "SECLEVEL=BSD" is ? I have never heard this one.
When I setup,
NIS master: SunOS4.1.3
NIS slave : DEC ALPHA (OSF1) UNIX
first, everything looks OK.
The problem I found is complicated and I can't explain well.
So, let me tell you the case expample.
There is a user "masahiro" .
His default gid is,
staff:*:10:masahiro
in /etc/group .
One day, he becomes "news" administrator and he wants to get the priviledge
of "news" group .
So, /etc/passwd is modifyed like,
staff:*:10:masahiro
news:*:6:masahiro
and
# (cd /var/yp; make group )
is executed in NIS master host. (SunOS4)
If the NIS client is SunOS, "netid" database is re-published
when group database is published automatically.
If "netid" is not published while "group" is published,
the NFS client (SunOS) can't get new privilege
when accesing remote NFS filesystem. (No problem in NFS master's disk.)
( In one word, the "netid" has to be published when "group" is published. )
When I setup NIS slave server on DEC ALPHA (OSF1) UNIX,
every Sun's NIS client machines looked DEC's NIS server (slave),
because our DEC host was very powerfull machine.
NIS master ----(netid)---> DEC (NIS slave) ----(no netid)---> NIS client
The NIS master is publishing "netid", but DEC has been cut the information.
So, the NIS client (SunOS) had "group access problem" I mentioned above.
What I want is,
just make DEC (NIS slave) pass the "netid" information to NIS client
instead of CUTTING it .
Don't you have any problems in Sun's clients
when you modified "group" file in NIS master ?!
(When your NIS client looks SunOS's ypserv, the problem can not be found.)
Is the SECLEVEL=BSD in /etc/svc.conf fix this problem ?!?!?
P.S)
I can't say the problem correctly even in Japanese . (^_^;
So, please make allowance me of my poor English explanations.
Thanks!
--
Masahiro Yanagisawa <masahiro_at_barclays.co.jp>
Information Technology Dept. BARCLAYS SERVICES (JAPAN) LIMITED.
# Disclaimer: Any views or opinions presented are solely those of the
# author and do not necessarily represent those of the Barclays Group.
Received on Tue Jun 18 1996 - 11:57:47 NZST