The NFS mount is actually set to ro (read only), so I wouldn't think (not to be read as it couldn't happen) the files would get corrupted. Stranger UV things have happened.
The file itself is not on a UV system. What I did was a CREATE-FILE then copied the file to the shared directory. Then I did a DELETE-FILE so it was no longer in the original UV's systems linkages. Now the only reference is via a VOC remote pointer. I will have to play around with this (Warnings taken, not lightly). Thanks for the info. George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Martin Phillips > Sent: Friday, October 24, 2008 5:05 AM > To: [email protected] > Subject: Re: [U2] RE: Triggers on a NFS file? > > > UV introduced the ALLOWNFS configuration option long ago with > a default > setting of 0 (no). When I deliver UV training, I take great care to > emphasise that setting this to 1 (yes) also means "it's all > my fault if the > file gets corrupted". > > > Martin Phillips ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
