Permissions are assigned as follows: Owner = admin user on the G4, Group=shareusers with R/W, and everybody=R/W. the same scenarios as (a) through (c) above occur.īoth shares are shared via SharePoints on a G4 running Tiger (non server version). If I mount share2 then run the script for share1. Clicking the Edit button in either (a) or (c) gives me an error that says Script Editor can't open the dictionary of the application because it is not scriptable.īoth scripts are saved as universal binary application bundles.īoth scripts work properly if neither volume is currently mounted when they are run. I get some random combination of the following: (a) an error dialog that says Disk some volume can't be found with an OK and Edit button, (b) proper operation of the script with share2 mounting normally or (c) same as #1 except the volume mounts when I click the OK button. If share1 is already mounted and I run the script to mount share2. what I want to do is keep share1 always mounted and only mount share2 when needed for the backup. I'm running into an issue when the second script is run. and created a second share on the server with identical share permissions as the original. Recently I reorganized my backup routines for the laptops. An applescript of the form mount vol works perfectly. my wife and I save all real data to the server instead of our local homedirectories. I've been using a similar method to this for years to mount an afp server volume on my laptop at home. I'm sure there is a better way of managing it ( could use automator to manage the disconnects too I'm sure ), but this is working really well for me right now. This removes the hassle of having connected drives when you go off network ( assuming you sleep when you move your machine ), and reconnects to the servers if they are available. Then, I add something like "umount /Volumes/SERVER_NAME" for each server that I have in the automator workflow to sleepwatcher's sleep script. Just add something like "open ~/connectToMyServers.app" to the script. If you create the automator workflow as described in the hint above, and then add it to sleepwatchers wakeup script, it will attempt to connect everytime your laptop wakes up. SleepWatcher allows you to use two scripts, one for on sleeping, and one for on waking up. However, the laptop does go to sleep whenever I close the lid, so that immediately points me to SleepWatcher. If you need more assistance, watch the screencast at the above link.Ī method similar to what I'm doing has been shown already, but I'll show what I have, since it seems to work really well for me:įirst off, my laptop is almost never turned off - and I almost never log out, so the login items trick isn't that useful to me. Add your new Application to your System Accounts Login Items.Save your workflow as a Workflow and Application.Click the Run button to test your workflow.Click and drag Connect to Servers under the Get Specified Servers section.Repeat the previous step for the remaining shares you wish to automount.Type smb://server name/share name in the Address: field, and click Connect ( smb://nas/mp3 in my example).Click on the + sign in the Get Specified Servers window.Click and drag Get Specified Servers into rightmost screen section.Take note of share names and network server name on a piece of paper.Click on server name (nas in my example). ![]()
0 Comments
Leave a Reply. |