Archive for ‘osx Server’ Category
If you ever need to scan the airwaves for wireless accesspoints, you might want to try the new AirRadar. Yes, there are other programs out there that do similar things (AirStatz or iStumbler), but AirRadar also supports GROWL which is kinda nice
Have you ever had problems ejecting a disk or emptying your trash under OSX. Did you waste time trying to find the offending program. Well “What’s Keeping Me?” is for you. Just run it the next time you get one of these errors, tell it the name of the file that’s giving you grief and it will return a list of processes that have locked that file. Then you have the option of killing those processes. Nice little free util to add to your collection.
Posted on 17:07, July 1st, 2008 by Many Ayromlou
One of the things I don’t really like about OSX Leopard is the fact that everytime you take a screen shot of a window (Command-Shift-4 followed by Spacebar), it put’s a — for us bloggers — not so good looking shadow around the capture. Well not anymore, use the following command to disable the effect:
Just when you thought your command line life was getting boring, we discover these happy tunes for your cut/paste pleasure. Just select the entire line, copy it, open a terminal window, paste it followed by Enter and marvel at your Mac. Yeah it’s a OSX thing and works best under 10.5, so if you’ve got Vista/XP/Linux, this might be a good enough reason to do the switcheroo :-).
Came across this tip today and I thought it might be useful to some of you out there. OSX, as great as it is, has always had this (atleast) one shortcoming for me. The stupid date display in the menubar. Why did they decide to hide the actual date/day of the week is beyond me. Yes, you can go and grab Magical, I know…..But that’s yet another program that needs to be loaded. There is a simpler solution. Follow the steps below and you can prettify your date display too :-).
Wow, Apple must be doing something right. According to research specialist SCRI, in 2007 Apple took 49% of the US professional editing marketing with Avid trailing on just 22%. There were a lot of rumors during NAB this year that Apple was gonna sell of it’s pro-video division to [your-favourite-video-company] (I heard Thomson/GV). At the time, I thought that would be a dumb thing to do and I said so. It turns out Richard Townhill, Apple’s director of marketing for professional video applications agrees with me. In this TVBEurope report Mr. Townhill says:
referring to the FCP unloading rumors. He then went on to say — about the recently released Final Cut Server:
Clearly Apple sees Final Cut Server as another mass market product, and why not, when you own 49% of the market, the only way to go is UP afterall.
The long awaited Apple Final Cut Server was released today, ahead of this years NAB show. It’s been a long time coming (more than two years almost), but you can finally have your cake and eat it too. From Apple’s FCS page:
Posted on 19:21, March 27th, 2008 by Many Ayromlou
Apples remote desktop service is great and it comes in handy, but what happens when you’re 5000 miles away from your desktop, only to find that remote desktop is turned off. Dooohhhh. Well here is a quick tip to turn the damn thing on and off in a second through a remote ssh connection. To turn on the service, ssh to your machine and issue the following commands:
So after pulling out my (non-existent) hair for the past two days I think I’ve finally figured out how Apple deals with Virtual Web Servers under Leopard. If you go to the Server Admin and look under the Web Service you’ll notice the Sites icon and if you’re like me you assume that since Apple obviously has gone to great lengths to design a unified interface for Admins, that they would give you access to all the basic/intermediate options. NOPE!!!!! Read on and see if you’ve run into any of these problems.
1) First of all, I don’t understand why apple’s webserver (apache) is configured to automagically reroute you to http://www.mysite.com/groups/workgroup when you really just want to get to the index.html in the (so called) document root. Apple assumes that when you type http://www.mysite.com that you really want to go to http://www.mysite.com/groups/workgroup. That is plain dumb. And to make it worst there is no place in the interface to disable (or modify) this. So get out your terminals, we’re gonna do some surgery:
2) And while we are on the subject of obscurity, If you want to have multiple virtual hosts with their own blogs/wikis hosted under their individual virtual hostnames, Apple strikes again by hiding the options and only enabling the workgroup services under the “main” webserver address. Here is how you fix that:
Hope this helps…..The above 2 problems are discussed (not in great detail) under the following two Apple Support Discussions:
While the world was busy trying to figure out how to sync their palm pilots to Windows 98 (or was it 95) Andrew Tridgell was working on his thesis……Rsync. The endall-beall in the world of syncing. You see, if you’ve ever tried any syncing program before you’ll appreciate the ease with which rsync works. You’ll also see the efficiency of it’s algorithm in dealing with changes/updates, and for that you can thank Andrew. I’m just gonna show you how to use this excellent tool along with ssh (another must have/must use free software utility) to setup automated secure backups between two different platforms.
For the purpose of this article I’m using a PowerMac G5 with a 1TB Firewire disk hanging off it as my backup server. As my client I’m using the departmental research server (yes, forget that it’s a server, in this exercise it’s a CLIENT).
So first we need to make sure we have the tools: ssh and rsync. They are already part of my distribution (SuSE Linux 10.1 on the client and OSX 10.5.1 on the server) so I didn’t have to install anything. You want to make sure that your rsync uses protocol version 2.x.x on both sides. (type: rsync –version on your machines to see the protocol version).
Note: You can also grab RsyncX for older OSX versions and/or cwRsync for windows.
Step 1. Is to remove the interactivity that happens during an ssh session (ie: password prompt). To do this we must generate passphraseless keys that we can initially manually exchange between our machines. So in our case we want to grant access to our client machine — via ssh — from the server. Now here is were things get a bit OS specific. Under OSX there is no root account (atleast not one you can log into) by default. In my setup I want to allow firstname.lastname@example.org (OSX machine) to have access to email@example.com (Linux machine), so here is what I had to do.
On the OSX machine (server or machine initiating the rsync session) login as the standard user/admin and issue the following commands:
Now you need to transfer the id_dsa.pub key file to your client somehow. I do this just using ssh again. If you want to be totally super secure you can stick it on a usb key and walk it over to your client machine. So still on the server (OSX) machine I do the following (still in roots account, so be careful):
Now, to verify, while still logged into root on the server (OSX) try to ssh to your client machine (using root’s account on client). If everything works you should be able to log into root’s account on the client (Linux machine) without a password prompt. If you’re prompted for password, stop here, and redo/recheck your procedure.
Step 2. Pheew…..You made it, that was the hard part….the rest is pretty simple. Now we just need to test to make sure things are running smoothly and once that’s done we can automate everything using a cron job (Step 3.). So lets start our test run. For this I’ve chosen to backup the /etc directory on the server (lots of small files, nothing earth shattering) and my chosen path on the server is /Volumes/TERADISK. This is where OSX mounts my firewire drive (your milage may vary). I’ve created a folder on TERADISK called FULLBACKUP, which I use to have rsync house my backups. So to test issue the following command as root (yes still, so be carefull) on the server:
Step 3. Well we’ve reached the end. All you have to do now is to use crontab -e command while still logged in as root on the server to add rsync entries for folders you want synced between the client and the server. Note that I do NOT backup absolutely everything off the client, only specific folders (and their subfolders ofcourse). I’m pretty sure that rsync will get confused if you try to sync things like your dev directory from the linux client. In my cron I have the following:
That’s it. Hopefully this has been useful…..