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 |
To: buildhelp Cc: admin, grava, grist Subject: Date: Tue, 27 Apr 93 08:38:36 +28716 From: ric X-Mts: smtp CAn someone from reng have a look. AWASTED has it mounted correctly ------- Forwarded Message >>Return-Path: grava >>Received: by flambe.zk3.dec.com; id AA20311; Mon, 26 Apr 1993 19:01:35 -0400 >>Received: by awasted.zk3.dec.com; id AA02542; Mon, 26 Apr 1993 19:01:31 -0400 >>Message-Id: <[email protected]> >>To: reng, admin >>Cc: grist >>Subject: access to agosmaint.nightly >>Date: Mon, 26 Apr 93 19:01:31 +28716 >>From: grava >>X-Mts: smtp >>I can't seem to get to agosmaint.nightly from awasted. odemount -list >>tells me it's there and mounted: >><awasted-/home/grava> odemount -list >> STATUS AVAILABLE PROJECTS >>- -------- ---------------------- >>... >>Mounted agosmaint.bl2: >>Mounted agosmaint.nightly: >>Mounted agosmaint.pre.bl3: >>... >>but: >>mksb -back agosmaint.nightly -dir ~/josh/sandpile.d/sub.d -m alphasub >>User rc file, /home/grava/.sandboxrc, does not exist; will create it. >>>> WARNING in mksb: >>>> agosmaint.nightly is not a legal, accessible sandbox. >>>> Will prompt for this information. >>No known current builds to pick from. >>... >>help, please... >>thanks, >>bill >>------- End of Forwarded Message
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
6.1 | AOSG::TAPPAN | Wed Apr 28 1993 11:10 | 16 | ||
To: grava Cc: ric, reng, [email protected], buildhelp, grist Subject: re: access to agosmaint.nightly Date: Tue, 27 Apr 93 10:09:03 +28716 From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf> X-Mts: smtp Bill, try it again. There was an error in the /usr/sde/build_list for agosmaint.nightly which caused an error when the system tried to look up where it lived. This has been fixed, and it should work properly now (unless there some other error). This problem definitely would have caused the symptom you saw. -josh ------- Forwarded Message |