Workaround for .nfs files on target server

System

Customer is using opendeploy 5.5.1
She deploys to there production server.
Solairs locks file with .nfsxxx.
On transactional deploys this fails. Customer is looking for a way around the .nfsxxx file issue.

This is what she says in the case notes:

here's an article explaining the mysterious .nfsXXXX files that are causing our problems:
http://www.cse.unsw.edu.au/faq/questions/help-nfs.html

these .nfsXXXX files are the solaris equivalent of the IIS lock, to accomodate files that are currently "in use"...but if iplanet or whatever user/application doesn't release that file, the .nfsXXXX cached version won't die...the existance of a .nfsXXXX file in a directory will cause an attempt to delete that directory to fail...which means that a transactional OD deployment will fail when it tries to do the "cleanup" portion of deleting the original directory which has been renamed to *.iwold but still contains the .nfsXXXX cache file...

that's the problem...I can see 2 possible solutions...1) is there a way to override/kill these .nfsXXXX files permanently, or 2) is there a way to tell opendeploy to only warn on a failure on a cleanup task, not fail the whole deployment?

thanks!
==========
Phil Czajkowski
Technical Support Engineer
Tel: 301-968-4621
Fax: 301-469-9276
Email: pczajkow@interwoven.com
Visit www.interwoven.com
==========
Customer Resources:
Customer Support - https://support.interwoven.com/
Training - http://www.interwoven.com/services/training/summary.html
Consulting / CM Resources - http://www.interwoven.com/services/consulting/>