-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automount triggered randomly #7
Comments
This also happens to me sometimes, unfortunately I don't know how to log the events that trigger the script.
|
Any updates on this? |
Sorry for the delay! I was travelling since last week and just returned home. Will try it tonight! |
Little update … I couldn't wait and updated on my Macbook. ;-) So far so good. After the first hour, automount just did as supposed to. When I trigger a network event (join/switch wifi, connect/disconnect VPN) the script runs – besides that I don't get any messages. I will install it on my iMac tonight and report back! |
Installed it on second Mac last night. After using both machines for the whole evening, it still triggers without obvious reasons, though less often. The Macbook is connected through Wifi, the iMac through ethernet. Isn't there the possibility to protocol launchd with all triggers/events? |
Unfortunately i don't know a way to log when or why a script is started via launchd :( |
It seems it tricky to solve this problem :) Maybe http://superuser.com/a/626919/325746 could help (only the watchpaths)? |
Sleepwatcher from http://www.bernhard-baehr.de/ looks promising, i will test it the next days, this could be a solution |
Hello Gerd
After using automount for two days on my machines, I see it triggered a little too often.
One machine is an iMac connected solely via Ethernet, the second one is a Macbook.
While the main events for triggering seem to work fine (change of network, reboot, waking from sleep (?)), automount gets triggered while nothing changes. I can't see a pattern, it seems randomly. Sometimes multiple times in a row.
Are the events that trigger the script logged? Can we see what happens there?
The text was updated successfully, but these errors were encountered: