Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: Schedule OS X software updates via script' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Schedule OS X software updates via script
Authored by: BjarneDM on Apr 10, '09 07:30:21AM
Really? If you're really that concerned about software updates and who ever not running them setup an @weekly cron job. as ron popeil put it: set it and forget it.

Well, launchd is for most scheduling issues an Apple recommended replacement for cron as well as most other scheduling services like inetd, xinetd and /etc/rc. With 10.5 Apple migrated all of their cron jobs to launchd. So, I've actually done as you recommend. And with the cache issue, running Software Update straight isn't an option - I'll still need to do it by way of my bash script.

Or you could just run ssh on a non-standard port like any sane person would do.

Any 'sane' person would understand that that's not possible as all outside access to any process no matter what port it's running under is complely blocked at the ISP level. I can't even ping the computer in question!



[ Reply to This | # ]
10.5: Schedule OS X software updates via script
Authored by: mzs on Apr 13, '09 11:59:08AM

About the ports. My dad would call a lot needing help with an XP computer at his house, so I tried to setup vnc so I could control his screen. I do not think it was the ISP, but rather the wireless router from the ISP that prevented incoming connections, which is actually a good thing in regards to a not well patched-up XP box.

What I did is I installed putty (an ssh client for windows) in addition to TightVNC (or maybe it was ultravnc, can't remember anymore) on his machine. Then I wrote a .bat file that would ssh into my machine at home forwarding port 5900 on his machine to 5910 on mine. Since it was an outgoing connection it worked. Then I would fire-up the vncviewer on the eMac with localhost:5910 and be able to see and control his screen on the XP box.

Then I had an account on my eMac for him that I would uncomment from the sshd_config file when he would call needing help. With this scheme he actually learned how to fix the problems himself very quickly and he has not called in years. It was a lot like a classroom working together on the same machine. We could both type and move the mouse and see what was going on while talking on the phone.

So the key thing was the whole make him do the connection out instead of me in. It was also nice since no one could control his screen without him knowing (the vnc server windows service was configured to only bind to localhost).



[ Reply to This | # ]