Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.sys.sgi
Subject: Re: Problems using Workspace with 3.3.1
Summary: don't do some of this
Keywords: workspace
Message-ID: <83384@sgi.sgi.com>
Date: 31 Jan 91 04:21:11 GMT
References: <1991Jan30.214131.24950@Neon.Stanford.EDU> <1991Jan31.005758.19797@odin.corp.sgi.com>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 16


> su
> cd /usr/etc/yp; make			( on the yp server machine)


It is much better to `cd /usr/etc/yp; ./ypmake` so that any local YP
configuration options are used.  The only disadvantage of using ypmake
is that it (currently) always dumps any error messages into the YP master log.

It is even better to be patient and to wait for cron to do this for you.  I
have often trashed YP databases by running (yp)make at the same time cron
was trying.  Generally, such damage is repaired the next time cron runs
ypmake, but until then life can be frustrating.


Vernon Schryver,   vjs@sgi.com