Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!uwm.edu!bionet!ames!claris!sts!octopus!pyramid!prls!mips!rogerk
From: rogerk@mips.COM (Roger B.A. Klorese)
Newsgroups: comp.unix.ultrix
Subject: Re: yp problem
Message-ID: <30175@servitude.mips.COM>
Date: 26 Oct 89 19:03:31 GMT
References: <26@e2big.dec.com> <13163@boulder.Colorado.EDU>
Reply-To: rogerk@mips.COM (0000-Admin(0000))
Organization: MIPS Computer Systems, Sunnyvale, CA
Lines: 21

In article <13163@boulder.Colorado.EDU> grunwald@foobar.colorado.edu writes:
>
>This brings up a good point; just as there is an /etc/svcorder that
>applies to the hosts table, it would be nice if there was an ordering
>spec to apply to e.g., services, etc. Perhaps /etc/svcorder should be
>extended (and cached to avoid reparsing all the file) to something
>like:
>
>svcorder
>---------
>hosts		local bind yp
>services	local
>protocols 	yp
>group	 	local
>passwd	 	yp

It's very doable: in fact, our next release of RISC/os for MIPS RISComputers
and RISCstations uses a similar file called vis.conf (Virtual Information
Service).  It allows specifications for hosts, services, protocols, group,
netgroup, and passwd, including search paths for "dns" (domain name server),
"file" and "yp".