Setperms Problems

[Tim Fischer]

Ok - I think I figured out what was going on the other day (though it 
wouldn't explain the processing issues, but we'll tackle that some other 
time).  We had some big problems this morning with files being locked.  
I'm still not too sure *what* was causing the locks, but those file 
locks froze dxmaint, setperms, *clerk, etc.  I'm chalking the setperms 
issue of last week to the file locking issue as well.

If this didn't make sense to anyone and they're curious, just email me - 
I'll try to explain it better.

Bob, thanks for the suggestions you had.  The -xv came in very useful to 
figure out which file was locked. 

Tim Fischer




Tim Fischer wrote:

> Bob Stockler wrote:
>
>> Tim Fischer wrote (on Fri, May 06, 2005 at 02:34:45PM -0400):
>>
>> | I was a little quick to write my last message.  I did run this 
>> again | without the "set -xv" and it did work this time, but the 
>> previous issues | I was referring to didn't work if I took the 
>> logging out.  Maybe I'm the | only one who's seen this?
>>
>> In some of those scripts that appear to work with your logging
>> enabled, add the set -xv line near the top, then execute the
>> script.  Then comment out the logging (don't delete it, just
>> comment it out) and execute them again.
>>
>> If there's any difference in their behavior with and without
>> the logging (which I doubt), you should see what the cause is
>> with the info provided by the set -xv.
>>
>> Bob
>>
>>  
>>
> Bob,
>
> The other "scripts" I'm referring to are FP processing tables (I 
> thought I had explained that earlier), so the -xv thing wouldn't work.
>