I use the app AutoMounter to keep several shared network drives connected to my MacBook Pro. I do this because Apple changed the way network shares connect, so that you always have to confirm the connect. AutoMounter, an app created by Pixeleyes and sold through the MAS, creates a link to the shared network drive in a container folder in the library folder, here: ~/Library/Containers/nz.co.pixeleyes.AutoMounter/Data/Mounts/. My understanding is that it does this in order to meet Apple’s sandboxing rules.
I am able to initially index the shared drive through DevonThink Pro Office, and view the files no problem. However, eventually (on a restart, for example) things go haywire. First the documents are not “seen” by DTPO, even though I am connected to the server, and can access the files directly through the finder. Then, the index disappears. As in, there are no records contained in the database. When I look at the folder of indexed documents, that started with 22,000+ records, there are no files, no subfolders, nothing. If I look at the Get Info pane for the folder, it appears to have a link to a folder in the container folder, but there is nothing in the database at all.
I have read other posts here that say you can index a folder in the container folder in your Library folder, but so far, this has not worked with a folder created by the AutoMounter app. Any ideas on how to keep the link to indexed files current, and not disappear, using DTPO?
I have contacted the developer of AutoMounter, but have not yet gotten an answer. Based on what I see in the container folder, it does seem to be the same. However, perhaps “under the hood” that link is actually dynamic.
Yes, I have checked that. What I don’t understand is that the whole index in the database disappears. With networked drives connected via the finder, when the drive is not connected I can still see the file listed in the database, but it gives me the error that the file cannot be located, when I want to preview it. Once the networked drive is reconnected, the file becomes accessible again. With the AutoMounter connection, the entire index in the DTPO database just disappears - there are no previews or anything. DTPO just shows “0”. Even when the connection is valid, and I can directly see the files through the finder. So it seems that there is something to the connection created by AutoMounter that results in DTPO loosing all references to the files and folders.
DEVONthink supports real volumes and recognizes whether they’re mounted or not. However, AutoMounter just uses a folder on the startup volume and if the folder doesn’t exist or isn’t the same any longer, then the indexed items are removed from the database.
That would explain it! If DTPO is open before AutoMounter creates the link to the shared drive in the container folder, DTPO sees the link as broken and deletes the indexed files. OK, so my choice is to go back to using the mapped drives through the finder, or always ensuring that AutoMounter is running when starting and using DTPO.
Is there any method for creating an index through DTPO that is more “permanent?”
I have done that in the past, butI find that if there is any blip in the connection, I get error messages (such as when I disconnect my MBP from my monitor, and the ethernet connection is disconnected). AutoMounter does not throw up errors, it just attempts to reconnect in the background, reestablishing the connect when I’m back on the network). It’s a matter of convenience, of course.
Actually, I created three Automator actions that load at boot that do exactly that. Unfortunately, whenever there is any disruption with the network, I get error messages. Thus, for example, if there is any delay in my wifi connecting, the Automator actions generate error messages. AutoMounter avoids all of that. It runs in the background, silently polling the network, and re-establishes network connections as and when they become available.
It would be handy if DTPO could handle indexing folders in other locations the way it handles indexes for network connections stored in /Volumes. Those indexes are kept even if a connection is are lost. I admit, though, that I do not understand the technical differences between those two setups. Here is a response that the developer of AutoMounter sent me:
Thanks for all of the prior responses. I understand that I may not be able to get DTPO to do what I would like with AutoMounter.
I meant fully manually double-clicking the alias after boot.
Having had to deal with server-based environments for many, many years, I have never been an advocate of automounting volumes on startup because of the problems inherent with dead / unresponsive servers, bad networks, etc. I had to train people to make double-clicking an alias a habit, but it’s no more effort than remembering your car keys before you get in the car.
You’re right, it seems that your system is the most effective means of avoiding the problems with dead/unresponsive servers (which is why I was so excited by the prospects of using AutoMounter!). Oh well! .
.