problems with /volumes if not connected

[matteaser]

Hi you all!

I recently tested another synchronisation sofware than SuperFlexible. I had the problem, that, when synching by accident (or by the scheduler) with my "data" share without connection it caused a problem with my /volumes-folder. (it created a folder /volumes/data on my hard drive, so the next time I connected to "data" it was spelled "data-1" and caused problems with the path.)

Anyway, now I use SuperFlexible and would like to know if this problem could appear or not. If yes, I have to be very careful only to run SuperFlexible when connected to the network drive. If not, I can run it careless - it would do its job only when connected.

Since I cannot test this I would be very happy if someone understood my problem and could answer me!

Thanks, Matthias

[superflexible]

I think that MacOS is mostly responsible for this problem. We have built several safety checks into the software to avoid it, but I can't guarantee it. Our software itself never creates a folder in /Volumes, but MacOS may sometimes do it.

Before starting a job, the latest version of our software makes sure that the volume reference number of any item below /Volumes is different from the system volume. That way, at least it will prevent copying files into a subfolder of /Volumes.

[superflexible]

Also, you can specify the network path under Special->Network Connections (or Mount Volumes). Then, the program will automatically see if the mount point changes. If MacOS decides to add -1 to the mount point, the program will see it and use that.

[matteaser]

I experienced that if the synch volumes are not connected SuperFlexible does'nt do anything allthoug scheduled. It says "can't access right path".
That's exactly what I wanted, so I'm happy with it!
Thanks for your replies!

Matthias