| Date Of Receipt: 28-MAY-1993 16:28:30.98
From: QUARRY::"[email protected]"
To: QUARRY::dlong
CC: QUARRY::odehelp
Subj: RE: aurous
The ode commands get default information from your default sandbox.
If your default sandbox is in /usr/projects/bugs, that might explain your hangs.
To get a better picture of why it's hanging, use the -debug and mark where the
hang occurs.
If you feel that ode is incorrectly accessing files in /usr/projects/bugs,
please submit a ptt with -debug output.
Thanks
--Kim
=============================================================================
From: RUST::QUARRY::dlong 28-MAY-1993 13:20:01.90
To: odehelp@DEC:.zko.quarry
CC:
Subj: aurous
Why do bci and workon now hang with the messge:
NFS server aurous not responding still trying
This is someones personal workstation. I do not understand
why I need access to it. My only reference to aurous is that
I mount a filesystem from it on /usr/projects/bugs. I use
nothing else from it. I have nothing in my PATH referencing it
and no symlinks I use pointing to it. The ode commands
are the only ones that hang. What's the deal?
-dl
|
| <<< SYS$SYSDEVICE:[NOTES$LIBRARY]BUILDHELP.NOTE;1 >>>
-< USG buildhelp questions/answers >-
================================================================================
Note 92.0 re: aurous & ode problems 1 reply
SMURF::FILTER "Automatic Posting Software - mail to" 42 lines 7-JUN-1993 16:03
--------------------------------------------------------------------------------
Date Of Receipt: 28-MAY-1993 16:25:48.93
From: MINSRV::"[email protected]" "Joshua M. Friedman ULTRIX SDE"
To: [email protected]
CC: [email protected], [email protected], [email protected],
[email protected]
Subj: re: aurous & ode problems
Jim, have you done anything funky which could account for this? There's
no reference to aurous in ode_fstab.
You said you were going to add a local automount map for aurous for
/usr/sde since we've removed automount support for it. Is dave somehow
picking this up?
-josh
------- Forwarded Message
Return-Path: dlong
Received: by quarry.zk3.dec.com; id AA28539; Fri, 28 May 1993 16:19:27 -0400
Date: Fri, 28 May 1993 16:19:27 -0400
From: David Long UEG <dlong>
Message-Id: <[email protected]>
To: odehelp
Subject: aurous
Why do bci and workon now hang with the messge:
NFS server aurous not responding still trying
This is someones personal workstation. I do not understand
why I need access to it. My only reference to aurous is that
I mount a filesystem from it on /usr/projects/bugs. I use
nothing else from it. I have nothing in my PATH referencing it
and no symlinks I use pointing to it. The ode commands
are the only ones that hang. What's the deal?
- -dl
------- End of Forwarded Message
|
| <<< SYS$SYSDEVICE:[NOTES$LIBRARY]BUILDHELP.NOTE;1 >>>
-< USG buildhelp questions/answers >-
================================================================================
Note 92.1 re: aurous & ode problems 1 of 1
SMURF::FILTER "Automatic Posting Software - mail to" 18 lines 7-JUN-1993 16:05
-< re: aurous & ode problems >-
--------------------------------------------------------------------------------
Date Of Receipt: 29-MAY-1993 10:10:32.51
From: QUARRY::dlong "David Long UEG"
To: jmcg jmf
CC: admin dlong odehelp reng
Subj: re: aurous & ode problems
I did a little experimenting and I think I know why it appears ODE needs
aurous when I'm using my sandbox. Something in ODE must attempt to touch
every directory in /usr/projects, possibly with a simple "ls -l /usr/projects".
I keep several NFS mounted filesystems in there on my machine so if any of
them are unavailable my machine will hang when I attempt to use ODE. I
think it's a bad idea for ODE to be looking for things it doesn't need in
this, or any other directory. In a complex NFS environment like ours this
all but guarantees a dependency on nearly every machine in the lab (and some
that aren't).
-dl
|