Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!pcserver2!kdenning
From: kdenning@pcserver2.naitc.com (Karl Denninger)
Newsgroups: comp.sys.mips
Subject: Re: Ypbind -- isn't detaching properly
Summary: This is a FAQ question
Message-ID: <1991Mar20.223800.20414@pcserver2.naitc.com>
Date: 20 Mar 91 22:38:00 GMT
References: <1991Mar13.162029@ria.ccs.uwo.ca>
Organization: AC Nielsen, Bannockburn IL USA
Lines: 30

In article <1991Mar13.162029@ria.ccs.uwo.ca> reggers@ria.ccs.uwo.ca (Reg Quinton) writes:
>We're running Risc/Os 4.51 on an M/120 and want this machine to be a YP
>(aka NIS) server. Of course there's nothing put together on the machine
>to do this so you have to build all the startup files from scratch.
>
>Anyways, I'm having some luck but one irritating problem is ypbind. When
>ypbind is started at boot time it just disappears. When the system is up and
>running I can start a version by hand and it will stay up and running as a
>proper daemon.  This sounds an awful lot like the problems we had with sylogd
>in earlier versions of Risc/Os.
>
>Has anyone else seen this problem? Has anyone got a solution?

Yes.

It is easy to fix.

Start it with a "nohup ypbind >/dev/null 2>&1".....

You want to do two "ypwhich" calls after that, with a 2 second delay (or
thereabouts) after that. The first will return a "no bound"; the second will
return the server name.  Then you're all set.

--
Karl Denninger - AC Nielsen, Bannockburn IL (708) 317-3285
kdenning@nis.naitc.com

"The most dangerous command on any computer is the carriage return."
Disclaimer:  The opinions here are solely mine and may or may not reflect
  	     those of the company.