Tiny Deathstars of Foulness

I prefer ClamXav, easy-to-use, light, with a good detection rate, and detects Win and Mac OS X virus.  Others: . avast . iAntiVirus (virus for Mac OS X only) . Intego X5 . Norton . Mcafee . Sophos . CA

November 29th, 2007

Posted In: Mac OS X, Mac OS X Server, Mac Security

Tags: , , , , , ,

WAN Acceleration has been a hot topic for some time.  But over the past couple of years the cost of acceleration technology has dropped drastically due to its emergence as a full-blown market.  Riverbed has jumped to the top of the leaders circle for a number of reasons, with Juniper, Blue Coat, Cisco, Packeteer, etc in its wake.  For the most part, all WAN accelerators are going to have a few things in common.  There are a pair of appliances, each with a disk that can cache files going between two points.  To some degree, the purchase of accelerator appliances should be driven by the protocols to be used.  For example, if you’re a purely Citrix shop then why would you bother to purchase another appliance – just don’t do it unless there is a specific option that you’re looking for. With Riverbed, they fit nicely for environments where a specific protocol isn’t being looked for – but instead where all traffic is to be accelerated.  They will compress the data more than it would be compressed over a standard connection, but will then one-up the competition by not requiring you to have a pair of devices but instead allow you to install client software so you can accelerate all clients on the edge, including those in hotels and at home.  To me, this is why they get to go to the top of the Quadrant.  But look out, Packeteer has announced a competing product and the rumor mill has it that Silver Peak and Juniper will shortly. 

November 28th, 2007

Posted In: Consulting, Network Infrastructure

Tags: , , , , , , , , , , ,

If you are interviewing for a job then research the company first.  Know what you can about the history, structure and mission and point out places where there is synergy between you and the company.

November 27th, 2007

Posted In: Interviewing

Tags: ,

I originally posted this at Leopard Server and wiki. It’s cool and it works. But when you’re first looking into it, it might seem a little confusing. So let’s do a simple walkthrough. Here we’re going to enable a wiki in advanced mode for a group called testgroup and we’re going to give a user called testadmin access to edit the wikis and create new ones. To get access to the wiki we’re going to assume a hostname of First, let’s go into Workgroup Manager and create a new group called testgroup. To do this, open Workgroup Manager, authenticate to Open Directory and click on the New Group icon in the toolbar. Enter a name for the group (testgroup for this example) and check the box for “wiki and blog.” Select the website to publish the wiki to in the Enable the following services for this group on field. Choose who can view and who can write to the wiki and click on the Save button. Now let’s create a user called testuser. In Workgroup Manager, click on the User list and click on New User. Now enter a name for the user and a password. Then use the Groups tab to put the user into the testgroup group. Now click on Save. Now that we have a user and group to give access to the wiki let’s go ahead and create a wiki. To do this open Server Admin. If the Web Service has not been enabled yet, click on the server name, click on Settings in the toolbar and then click on the Services tab and place a check in the box for Web. Now click on the web icon and click on the Settings tab. Select a theme for your site and click on Save. Now click on the Sites icon in the toolbar and click on the site you’d like to publish your wiki on. From here click on the Web Services tab and put a checkmark in the Wiki and blog box. Now click on Save. Then Start the web service. Now you should be able to open up a web browser and go to URL of the server. Remember, do this by host name and not IP. At this point, you’ll see the Groups tab along the top navbar. From here you can click on Groups and then click on the group you want to create the wiki for (testgroup for our test wiki). Now you’ll be asked for a username and password. Enter the testuser you created and the password that you gave to testuser. Now you can click on the + icon to create your first entry into the wiki. Let’s call it testpost. That’s it. You’ve now created your first wiki article on your new wiki server. Notice that if you enabled calendars and blogs that there will be icons for these in the top nav bar. You can customize everything you see on the screen to give it a more organizational look and feel. For example if you click on the pencil icon you will be able to rename the blog and customize the prebuilt information listed in the Welcome to your Wiki page.

November 26th, 2007

Posted In: Mac OS X Server

Tags: , , , , ,

Does a 31-17 win sound worthy of a little love in the polls?  I mean really, we beat Florida, we beat Auburn, we just lost to the ‘ole ball coach and the Vols.  I really wish we hadn’t of lost that game to SC?!?!?

November 25th, 2007

Posted In: Football

Tags: , , , , , ,

I originally posted this at So you need to empty your cache resolver, but you fire up your handylookupd but you’re getting a command not found error. What to do… Try dscacheutil, which let’s you do so very much more than lookupd. For example, using the -cachedump allows you to dump an overview of the cache contents. -cachedump has a slew of flags to get pretty granular with the output such as -entries and -buckets-configurationallows you to access detailed information about your search policy. -statistics allows you to view detailed information on statistics of calls. Examples of using these commands: Emtpy the DNS Cache Resolver: dscacheutil -flushcache Dump cache with user entries: dscacheutil -cachedump -entries user Lookup all the users on a system: dscacheutil -q user

November 24th, 2007

Posted In: Mac OS X, Mac OS X Server

Tags: , , , , ,

I originally posted this at For early Leopard adopters that don’t like the new look and feel of the dock, here’s a command to disable that Glass shelf look in your dock: defaults write no-glass -boolean YES killall Dock If you would like to revert the setting: defaults write no-glass -boolean NO killall Dock click on the code and choose run to activate or deactivate this setting

November 23rd, 2007

Posted In: Mac OS X

Tags: , , , , , ,

I originally posted this at The default “skin” of the WebMail server (SquirrelMail) in OS X server leaves a lot to be desired to some. So we thought that we would post some of the more popular skins/themes (or collections of themes) that we’ve been using so you can check them out: Happy skinning!

November 22nd, 2007

Posted In: Mac OS X Server

Tags: , ,

I originally posted this at Customizing the welcome message to new users of your iChat server is a fairly simple task. For this, we’ll look into the jabber configuration because jabber is the Open Source package that iChat Server is built on. When you first setup jabber the /etc/jabber directory will be created. Inside this folder will be a file called jabber.xml. If you open the jabber xml file and look for the “welcome” tag then anything between the "welcome" and"/welcome" will be the information that is shown in a welcome screen when a new user signs onto the iChat server. Before you edit the /etc/jaber/jabber.xml file make sure to back it up. For this example we will have all new users receive a message that says Welcome to the 318 iChat Server. To do this, delete or comment out the information between the existing welcome tags and add the following information: "welcome" "subject"318 iChat Server"/subject" "body"Welcome to the 318 iChat Server"/body" "/welcome" Save the jabber.xml file and you’ve now customized the welcome message for your iChat server. Note, for the purpose of this article the < and > have been replaced with quotes (”). However, you will need to use the < and > in your environment while using the Jabber.xml file.

November 21st, 2007

Posted In: Mac OS X Server

Tags: , , , , , ,

I originally posted this at If you want to enable the auto-population of buddy lists for users of your iChat server, use the following command: serveradmin settings jabber:enableAutoBuddy = no If you have a lot of users and this causes performance issues, consider disabling this feature again by using the following command: serveradmin settings jabber:enableAutoBuddy = yes

November 20th, 2007

Posted In: Mac OS X Server

Tags: , , ,

Next Page »