| Date Of Receipt: 9-JUN-1993 14:23:36.44
From: QUARRY::dlong "David Long UEG"
To: vandyck@DEC:.zko.quarry
CC: ajh dlong karp metsky odehelp reng sue woodburn
Subj: Re: more suggestions
>Do you have any backing trees/shared sandboxes that are mounted on
>usr/projects?
I have no backing trees mounted there, and if I did that would not be
under my control since odemount decides where to mount things.
I do have shared sandboxes and other NFS filesystems mounted there.
>ODE has no notion of usr/projects unless you have some sandbox in
>your environment that would reference it.
I believe the only reason it should be referenced is to get to the
specific shared sandbox under it. Nonetheless, certain ODE commands
do reference the parent directory of their sandbox for come reason or
I wouldn't be seeing this problem.
>I do not have user projects even mounted, nor do I use anything
>that would reference it. In my experience, usr/projects is not a good
>place for a commonly accessed build environment because so much other
>activity goes on there. If you have sandboxes there, I'd strongly suggest
>moving them elsewhere.
In other words you're saying I can't use shared sandboxes on production
machines. This directory is the standard place to put all project areas.
If ODE insists on looking at everything in the sandbox's parent directory
then ODE is broken. The alternative is to place every shared sandbox
located in the production environment in its own unique parent directory.
That should not be necessary.
By the way I don't think that much other activity really goes on in
/usr/projects since virtually every directory in there on any production
machine (and most workstations) is a filesystem unto itself.
-dl
|
| Date Of Receipt: 9-JUN-1993 14:33:58.36
From: FLUME::jmcg "Jim McGinness"
To: flume::dlong, flume::vandyck
CC: flume::ajh, flume::karp, flume::metsky, flume::odehelp, flume::reng,
flume::sue, flume::woodburn
Subj: Re: more suggestions
This sounds like a problem related to the abyssmal implementation we
have for getting the current working directory, which involves reading
and stating the contents of ".." all the way back to the root. Some
of the shells insist on doing this at startup, some of the ODE commands
may well do it, too.
-- jmcg
|