Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm writing an internal tool for my company that will need to probably always have access to a samba share. How can I always ensure that the drive is mounted at the same address /Volumes/... or have the Flask application connect with a Python library? Ultimately, I could just change the application to manipulate files on the local machine but it isn't preferable.

What would be the most sustainable / efficient way to implement?

share|improve this question

migrated from Dec 3 '11 at 15:56

This question came from our site for professional and enthusiast programmers.

I need you to clear something up, are you talking about mount persistance (i.e. ensuring the mount is always there on the client end) or ensuring that the share is very resilient at the server end? – Chopper3 Dec 3 '11 at 16:01

Although you're ultimately interacting with files using python, this question feels much more like one for serverfault or superuser, both of which have more samba-tagged questions than stackoverflow does.

As for the question itself, I am not intimately familiar with OSX, but on my linux installation I really like autofs, a system daemon that automatically mounts network file servers (including nfs and ssh also). See this link with some basic setup steps. Alternatively, of course, there's always the standard way of connecting to network shares.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.