| 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: 8-MAY-1996 15:05:50.65 From: KAMLIA::dcj "David Jedlinsky USG" To: odehelp@DEC:.zko.kamlia CC: Subj: [dcj: Problems with mksb and bco] We rebooted the offending machine (psycho), and the problem went away. I have no clue why it stopped working. -Dave Jedlinsky [email protected] MLS+ Release Engineering >Date: Wed, 8 May 1996 10:54:54 -0400 >From: David Jedlinsky USG <dcj> >To: odehelp >Cc: dcj >Subject: Problems with mksb and bco > > >I'm having a problem running mksb and bco on our build machine; they >hang with no error messages. I can ^C the mksb, but not the bco. >'bco -odedebug cvs' echos nothing before hanging. I don't know if >other commands are affected. > >The mksb command gets this far: > >psycho:devbld-274> mksb -back /usr/sde/osf1/build/ptos.bl10 test_ptos >creating new set: David_Jedlinsky_test_ptos, setdir: . >creating lock file for new set. >[ creating /oldbacks/devbld/test_ptos/tmp ] >/oldbacks/devbld/test_ptos/tmp: created directory >drwxr-xr-x 2 devbld system 512 May 8 10:52 /oldbacks/devbld/test_ptos/tmp > >...and then hangs. I can abort at this point, but I have to undo the >partial sandbox. > >We're running ODE 3.0 on psycho.zk3.dec.com (V3.2C). The system has >worked with this configuration until this morning. > >Any ideas? > >-Dave Jedlinsky >[email protected] >MLS+ Release Engineering
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2264.1 | Re: [dcj: Problems with mksb and bco] | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Wed May 08 1996 16:49 | 28 |
Date Of Receipt: 8-MAY-1996 15:10:20.09 From: KAMLIA::johnf "John Flanagan USG Test Johnf Tools Group 08-May-1996 1503" To: David Jedlinsky USG <[email protected]> CC: [email protected] Subj: Re: [dcj: Problems with mksb and bco] The ptos.bl10 backingtree that you were backed by is exported from nsa, which went down a couple of times in the past 24 hours. I'm willing to bet this is what messed you up [as the kerberos authentication is authorized on a per host basis when you enter a workon]. When nsa went away, the authorization probably got lost and ode became confused. John -- ______________________________________________________________________ John Flanagan enet: [email protected] MS: ZKO3-3/W20 decnet: flume::johnf USG Release Management (603) 881-1719 110 Spitbrook Road (DTN) 381-1719 Nashua, NH ______________________________________________________________________ | |||||