Setperms Problems
Tim Fischer
tim.fischer at trinitytransport.com
Mon May 9 13:07:56 PDT 2005
It was actually locked on the file system level.
Tim Fischer
Bob Stockler wrote:
>Tim Fischer wrote (on Mon, May 09, 2005 at 03:49:07PM -0400):
>
>| 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.
>
>You're welcome, but I don't think filePro lockfiles could have
>any affect on how setperms works. It's a shell script, and the
>shell has no notion of filePro lockfiles, other that they are
>regular files.
>
>Bob
>
>
>
More information about the Filepro-list
mailing list