[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

1550.0. "error on .sandboxrc" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Fri Jun 23 1995 13:35

Date Of Receipt: 	13-JUN-1995 15:35:33.30
From: 	SMURF::ALPHA::duerksen "Steve Duerksen USG"
To: 	odehelp@DEC:.zko.alpha
CC: 	duerksen@DEC:.zko.alpha
Subj: 	error on .sandboxrc

Hi-

PROBLEM:
This is to report a problem, even though I have a workaround.
The problem is with any ode command that needs/reads $SANDBOX.
The error message is "can't parse sandbox rc".
The same conditions in other people's machines/sandboxes
doesn't stimulate the problem, for unknown reasons.

Seems "sbinfo" (and other more important commands, of course)
fail (sometimes!) after "workon", BUT not after "workon -sb p".
This despite the fact that "p" is my default.

APPARENT CAUSE:
The env var $SANDBOX is set to "(default sandbox)" in the first
case, and to "p" in the second case. The ode man for sbinfo
says it should work either way, but it doesn't.
My workaround, natch, is to not rely on the default, i.e.
I always use "workon -sb whatever", and thus the problem goes away.

SPECULATION:
Possibly related is my use of automount. When I'm inside vi
and write to a file, e.g. ":w ~/qq" it says "too many files"
as if "~" is somehow expanded to more than one (albeit
equivalent) path, like "/tmp_mnt/home/duerksen" and
"/home/duerksen". I have to say ":w /home/duerksen/qq".
I'm only guessing this is related to the sbinfo problem.

-Steve
T.RTitleUserPersonal
Name		DateLines
1550.1Re: error on .sandboxrcAOSG::FILTERAutomatic Posting Software - mail to flume::puckFri Jun 23 1995 14:2363
Date Of Receipt: 	14-JUN-1995 12:39:30.85
From: 	SMURF::WASTED::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	duerksen odehelp
CC: 	
Subj: 	Re:  error on .sandboxrc

Steve, can you please file a PTT report with gen-ptt.  Instructions are
in our web page, http:://nsa.zk3.dec.com/rengweb under ODE Help -
Reporting problems.

thanks!		-josh



---------
From duerksen  Tue Jun 13 15:34:39 1995
Delivery-Date: Tue, 13 Jun 95 15:34:44 -0400
Return-Path: duerksen
Received: from alpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.0/1.1.8.2/16Jan95-0946AM)
	id AA16140; Tue, 13 Jun 1995 15:34:39 -0400
Received: by alpha.zk3.dec.com; (5.65v3.0/1.1.8.2/20May95-1022AM)
	id AA11865; Tue, 13 Jun 1995 15:34:03 -0400
Date: Tue, 13 Jun 1995 15:34:03 -0400
From: Steve Duerksen USG <duerksen>
Message-Id: <[email protected]>
To: odehelp
Subject: error on .sandboxrc
Cc: duerksen
Status: R


Hi-

PROBLEM:
This is to report a problem, even though I have a workaround.
The problem is with any ode command that needs/reads $SANDBOX.
The error message is "can't parse sandbox rc".
The same conditions in other people's machines/sandboxes
doesn't stimulate the problem, for unknown reasons.

Seems "sbinfo" (and other more important commands, of course)
fail (sometimes!) after "workon", BUT not after "workon -sb p".
This despite the fact that "p" is my default.

APPARENT CAUSE:
The env var $SANDBOX is set to "(default sandbox)" in the first
case, and to "p" in the second case. The ode man for sbinfo
says it should work either way, but it doesn't.
My workaround, natch, is to not rely on the default, i.e.
I always use "workon -sb whatever", and thus the problem goes away.

SPECULATION:
Possibly related is my use of automount. When I'm inside vi
and write to a file, e.g. ":w ~/qq" it says "too many files"
as if "~" is somehow expanded to more than one (albeit
equivalent) path, like "/tmp_mnt/home/duerksen" and
"/home/duerksen". I have to say ":w /home/duerksen/qq".
I'm only guessing this is related to the sbinfo problem.

-Steve