| 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: 4-JAN-1994 11:47:12.91 From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE" To: [email protected], [email protected], [email protected] CC: [email protected], odehelp@wasted:zko.dec Subj: Re: Wondering about ODE Dick, this "Waiting for sandbox lock" means that you have another "b-command" process still running in your current sandbox. The sandbox environment uses your own <sandbox>/src/.BCSlock file to coordinate multiple actions. If you know you're not doing anything else in the sandbox, just remove the .BCSlock file; a new one will get created the next time you bci or whatever. This probably was the result of a ^C not being handled well by ode. It's not related in any way to the lastin/buffer changeover. -josh -------- From [email protected] Tue Jan 4 10:16:05 1994 Delivery-Date: Tue, 04 Jan 94 10:16:06 -0500 Return-Path: [email protected] Received: from caliph.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA17708; Tue, 4 Jan 1994 10:16:05 -0500 Received: by caliph.zk3.dec.com (5.57/ueg-15Nov90) id AA01045; Tue, 4 Jan 94 10:16:02 -0500 Date: Tue, 4 Jan 94 10:16:02 -0500 From: [email protected] (Cum dignitate otium) Message-Id: <[email protected]> To: [email protected], [email protected] Subject: Wondering about ODE Cc: [email protected] Whe I try to do a b-command (specifically, bco or bci) I get this message: [ Waiting for sandbox lock via flock() ] Things then come to a screeching hang, although I can ^C out. Are we still connected to lastin, and is it sick? -dick
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 498.1 | Re: Wondering about ODE | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Jan 11 1994 15:55 | 18 |
Date Of Receipt: 4-JAN-1994 12:16:54.74 From: CALIPH::binder "Cum dignitate otium" To: demers, jmf, wharton CC: odehelp Subj: Re: Wondering about ODE Josh, That was indeed it. When ronyon was hung yesterday, I ^C'ed out of a bco -u command, and the shell prompt never came back. (Oor maybe it did come back after I went home.) In any case, I still had hung processes of bco -u and authcover - I killed those, deleted the .BCSlock file, and things worked fine. Thanks! -dick | |||||