Skip to content

Inconsistent behavior with mounts under /Volumes

If the default mount directory is /Volumes, there may be subdirectories with SHARENAME-1 and the share was mounted under the -1. I suspect this is due to setting the shares to "undefined" during a network change or sleep trigger. This causes the shares to be mounted before the system times out for the existing mount:

  • mount is present
  • network changes
  • all mounts are set to "undefined"
  • network is back
  • mount is triggered, the previous mount directory is still there
  • mount occurs under /Volumes/directoryname-1"

A possible solution:

  • The status of mounts after a network change or sleep trigger will not be set to "undefined" but will retain its current status.
  • The routines that currently skip shares with a "mounted" status will first check the mount directory. If it is a filesystem mount (FileManager.default.attributesOfItem(atPath: atPath) == 2), do nothing; otherwise, set the mount status to "undefined".
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information