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 |
Date Of Receipt: 26-APR-1996 15:00:40.55 From: QUARRY::"[email protected]" "26-Apr-1996 1454" To: [email protected] CC: [email protected], [email protected] Subj: Still looking for help on creating v32supportos sandbox on HW6 system I've heard nothing back yet, Paul ------- Forwarded Message Return-Path: grist Received: from localhost by kenmore.zk3.dec.com; (5.65v3.2/1.1.8.2/06Mar95-0157 PM) id AA25845; Mon, 22 Apr 1996 11:04:48 -0400 Message-Id: <[email protected]> X-Mailer: exmh version 1.6.2 7/18/95 To: odehelp Cc: grist Subject: creating v32supportos sandbox on HW6 system Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Apr 96 11:04:48 -0400 From: "Paul Grist - UNIX Hardware Group" <grist> X-Mts: smtp I am having trouble accomplishing this and get the following everytime I try anything new to fix it: [toves..grist] mksb -back v32csupportos v32c_spool creating new set: Paul_Grist_v32c_spool, setdir: . creating lock file for new set. [ creating /usr/staff/grist/pools/v32c_spool/tmp ] /usr/staff/grist/pools/v32c_spool/tmp: created directory drwxr-xr-x 2 grist system 512 Apr 22 10:38 /usr/staff/grist/pools/v32c_spool/tmp bco: unable to lock via lockf() /usr/staff/grist/pools/v32c_spool/src/.BCSlock errno=77: No locks available >> WARNING in workon: >> failed to make lock file using bco. Status 1. [toves..grist] toves.zk3.dec.com is a sandpiper, new HW6-BL4 install. I followed instructions from the release engineering ODE set-up page and even ran the script. I re-ran nfssetup twice to enable locking and even rebooted. I can get my kerberos ticket fine, but never successfully make the sandbox. My sandbox area is an NFS mount from my V4.0 (rev 375) workstation. I'd appreciate any help or hints, After discovering the hard way that you can not build V3.2-anything on a V4.0 system, I'm now behind getting some patches ready in time for MP2 merges. Paul ------- End of Forwarded Message
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2249.1 | Re: Still looking for help on creating v32supportos sandbox on HW6 system | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon May 06 1996 17:31 | 17 |
Date Of Receipt: 26-APR-1996 17:45:26.96 From: QUARRY::"[email protected]" To: [email protected], [email protected] CC: [email protected] Subj: Re: Still looking for help on creating v32supportos sandbox on HW6 system Paul, this problem looks like one which would affect all of your sandboxes? Confirm that nfslocking is enabled on all systems involved (your system and nfs server if one's involved). errno=77: No locks available sounds like a system resource issue. It may sound drastic but you could try rebooting. -josh | |||||
2249.2 | Re: Still looking for help on creating v32supportos sandbox on HW6 system | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon May 06 1996 17:42 | 16 |
Date Of Receipt: 29-APR-1996 09:00:46.38 From: QUARRY::"[email protected]" "29-Apr-1996 0854" To: Joshua M. Friedman OSF/UNIX SDE <[email protected]> CC: [email protected], [email protected], [email protected], [email protected] Subj: Re: Still looking for help on creating v32supportos sandbox on HW6 system Thanks Josh, The culprit was no lock daemons running on my V4.0 system where my sandbox area is NFS-mounted from for builds on the HW6 system. Paul | |||||
2249.3 | Re: Still looking for help on creating v32supportos sandbox on HW6 system | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon May 06 1996 17:42 | 10 |
Date Of Receipt: 29-APR-1996 10:29:40.58 From: QUARRY::"[email protected]" To: [email protected], [email protected] CC: [email protected], [email protected], [email protected] Subj: Re: Still looking for help on creating v32supportos sandbox on HW6 system Great - sorry it took so long to get you an answer; we've been somewhat overloaded lately. -josh |