|
|
A script to determine Maximum Transmission Unit
I wanted to use this to see if it would solve a problem I was having at work, but the instructions are incomplete - some of us would rather drill our own teeth than use Terminal (life is too short) and I don't know how to point that chmod command at my file. My real question is: there's a whole scripting facility built into OS X, with a script editor and all - geek value zero. Is there a way to test the MTU using that? And why not? The script as given is incompatible with Script Editor.
AppleScript not so easy...
Yes, this likely could be rewritten as an AppleScript, but for most people, AppleScript is actually a much more difficult language to learn, implement and use than shell scripting or perl - mostly because on the face of it simple commands like 'tell Application "Finder" to open the selected file' seem to work, but once the script becomes more complex than that elements of error checking and even syntax parsing become quite obtuse.
AppleScript not so easy...
Well that's interesting, but I've only ever once needed Terminal before (and I've been using OS X professionally from the start) and at least that time the ubergeek waas condescending enough to provide complete instructions. I found out by myself that I can drag a file into terminal to get the path, and did the chmod o+x thing - so nice and intuitive: nothing at all seemed to happen - and I still don't know how to 'run' the script I have. I know this site is for 'hints' but what does it take to actually tell us how to do something?
AppleScript not so easy...
Download the script and open a Terminal window. Change the permissions on the script so that the script is executable. It seems you know how to get this far. The next step is to type at the command line ./NAMEOFSCRIPTwhere "NAMEOFSCRIPT" is the name of the script you made executable. The "./" is command line-ese for "run what comes next." Gabester is right, however. If you really want control over your Mac the most direct way is the command line. Because of this, many advanced techniques will specify command line interaction. If you've been around Macosxhints for any length of time, you almost certainly know this to be true. That said, yes, the command line is scary for most GUI-only users. There is a learning curve to the command line but--and this is an important but--it is very simple to get started on that learning curve. You can learn a lot in twenty minutes that will make your Mac OS life much easier (and richer and complex) by dipping a toe into the "mysterious" waters of the CLI (command line interface). The best way is to get experience in a UNIX shop. But since you are a professional and, as you say, "life is too short," there is a great batch of OS X command line tutorials at Macdevcenter.com. The first tutorial is a great place to start since it is designed to help beginning CLI users with a "step by step [of] how to get comfortable with the Terminal". Happy travels.
AppleScript not so easy...
Thanks, but I still can't make it work - here's the session (I tried it twice because I couldn't figure out how many slashes were needed)
Welcome to Darwin! grant-thompsons-power-mac-g5:~ grant$ chmod o+x /Users/grant/Desktop/scriptmtuI might have a look at those tutorials if I ever have time but frankly, I want to use my computer, not futz with its vitals. I started out in the era of punched cards and men in white coats and thought back then there must be a better way. I see neither charm nor virtue in the CLI. As I said I've only used it once before, following a hint from this site. At least it worked that time (though it didn't help...) Maybe one of you wizards can tell me why Msoft Windows Service Pack 1 breaks OS X access to servers - in exactly the same way it was broken when 10.4 first came out. I'm running 10.4.4. mount_smbfs: error from NetrShareEnum call: exception = 382312522
AppleScript not so easy...
>Maybe one of you wizards can tell me why Msoft Windows
AppleScript not so easy...
> The "./" is command line-ese for "run what comes next."
A script to determine Maximum Transmission Unit
You can diddle file permissions from the Get Info dialog. Right-click (or CTRL-click) the object and select Get Info from the resulting menu.
A script to determine Maximum Transmission Unit
I've written an AppleScript to set the MTU, and it includes parts of this script to lookup the maximum MTU ... you can get it from my blog: http://www.torrfamily.org/tumbleseed/products/set-mtu/
--- |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.11 seconds |
|