Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!caen!umich!terminator!pisa.citi.umich.edu!rees
From: rees@pisa.citi.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: .rgyloc
Message-ID: <5056ffc4.1bc5b@pisa.citi.umich.edu>
Date: 13 Mar 91 13:39:17 GMT
References: <9103121433.AA01966@tech.perpk.nt.com> <50528780.20b6d@apollo.HP.COM> <5053fb08.3593b@digital.sps.mot.com>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 11

In article <5053fb08.3593b@digital.sps.mot.com>, chen@digital.sps.mot.com (Jinfu Chen) writes:

  If this file is to supposely open, put it somewhere else, like
  /sys/node_data/systmp. How can a sys_admin not be panic when
  .rgyloc is sitting in the same directory as rc* files?

It's not a temporary file, even though it's a cache.  It wants to survive
reboots.

And I don't see how having it in the same directory with the rc files makes
any difference one way or the other.