On 13-Feb-2014 04:58 -0800, rob@xxxxxxxxx wrote:
Mimix only puts the lock on the target machine. It's to stop idiots
like me from changing the file on the target machine when all changes
should be coming from the primary. <<SNIP>>

As I recall the locking is optional\configurable. The /mimixing/ of the system file [in the quasi-user-library QUSRSYS] might best be configured without that locking, to avoid impacting legitimate work if\when performed on the target system.

If the OS is issuing an incorrect error [e.g. implied EACCES vs an expected EBUSY] due to the locking however, that is a separate issue.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.