| Date Of Receipt: 21-FEB-1994 21:01:21.14
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE 21-Feb-1994 2059"
To: shashi@wasted:zko.dec
CC: odehelp@wasted:zko.dec
Subj: Re: busbmit problem on gold
for some reason, the gold bsubmit.hold lock file (logs/lock_hold) did not
get cleaned up from an operation at about 5:20 -- I'll remove it now and
your submit will pick up if you haven't killed it...
-josh
------- Forwarded Message
Return-Path: shashi
Delivery-Date: Mon, 21 Feb 94 18:31:13 -0500
Return-Path: shashi
Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/03Feb94-1150AM)
id AA23463; Mon, 21 Feb 1994 18:31:09 -0500
Received: by wasted.zk3.dec.com; id AA28233; Mon, 21 Feb 1994 18:30:17 -0500
From: Shashi Mangalat USG <shashi>
Received: by amethyst.zk3.dec.com; (5.65/1.1.8.2/28Dec93-0905PM)
id AA01630; Mon, 21 Feb 1994 18:30:16 -0500
Date: Mon, 21 Feb 1994 18:30:16 -0500
Message-Id: <[email protected]>
To: odehelp
Subject: busbmit problem on gold
I get the following when submitting to gold:
> Lock file is temporarily unavailable. Waiting.................
Since I had done a kill of a previous try, I thought I could have left
the files in the hold state. But bsubmit.hold doesn't have my files in it.
I ran busbmit with '-debug -verbose' and found out that it is waiting
on lock_hold:
>>> DEBUG INFO in lockhold:
>>> file, lock_hold, already locked.
I don't know if I had it locked in my previous attempt, but how do I
clear the lock? I checked the lock_hold file, which is a directory(?)
with read/write (no execute either!) for owner only.
Thanks,
- --shashi
------- End of Forwarded Message
|