When Disk-Arbitrator is active, no auto-mounts can take place. So far so good. But: I have TimeMachine automatic backups activated, and so TimeMachine complains loudly every 30 minutes, because the (Network-)Backup Volume can be found, but cannot be mounted (because thats what Disk-Arbitrator does when active).
The situation is a bit tricky, because of the way TimeMachine performs mount operations:
First, the Network Backup Volume gets mounted, and after that, TimeMachine tries to take a specific file on that Network Volume and mounts it (as an image) to the local filesystem.
Two possible solutions:
Make Disk-Arbitrator check on activation wether automatic backups with TimeMachine are active, and make Disk-Arbitrator disable automatic TimeMachine backups for the time the "Activated"-Tick is set in Disk-Arbitrator. Surely when Disk-Arbitrator is de-activated or quit, the "TimeMachine automatic backups"-status should be restored to whatever it was before activating Disk-Arbitrator.
Somehow detect mount attempts which relate to TimeMachine backups (or even Network Volumes in general...) and let them go through untouched, even if Disk-Arbitrator is active.
When Disk-Arbitrator is active, no auto-mounts can take place. So far so good. But: I have TimeMachine automatic backups activated, and so TimeMachine complains loudly every 30 minutes, because the (Network-)Backup Volume can be found, but cannot be mounted (because thats what Disk-Arbitrator does when active). The situation is a bit tricky, because of the way TimeMachine performs mount operations: First, the Network Backup Volume gets mounted, and after that, TimeMachine tries to take a specific file on that Network Volume and mounts it (as an image) to the local filesystem. Two possible solutions:
Am I missing something? And other ideas/hints?