Marcus,

I am guessing here, but is this the situation where you would use the 
LOCKED_FILE_ACTION=SKIP directive in your bp.conf ?

We have Essbase in our shop and it will lock files ( a lower case l (ell)  will 
be present when viewing the permissions on a particular file ); the man page 
refers to it as "mandatory locking" on a
SUN server; before we specified this, our backup would hang and not complete; I 
am guessing that F_UNLCK is File_UNLoCK. Am I close ? Do you have files that 
are locked ?

Sorry if this is off base .....

john


-----Original Message-----
From: Eikenberry, Marcus - CIDS-2 [mailto:mjeikenberry AT bpa DOT gov]
Sent: Friday, July 18, 2003 11:10 AM
To: Veritas-Bu LIST (E-mail)
Subject: [Veritas-bu] F_UNLCK failed


Anyone know any information about the error "F_UNLCK failed"?   I asked about 
it once before with no reply and I looked through the archives for this group.  
Two other people have asked about it as
well with no reply.   Does anyone have any info about what the "F_UNLCK failed" 
error is? 

Marcus Eikenberry
Server Operations
United States Department of Energy
Bonneville Power Administration
503.230.3300

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu