Thanks buddy, I can't see it winning but if it does I will do a big review of it compared with my Bandicoot, they are both of similar size !!!! <img src="/ubbthreads/images/graemlins/thumbup.gif" alt="" />

Got you covered on this one. <img src="/ubbthreads/images/graemlins/thumbup.gif" alt="" />

The top five from that poll go through to the final poll so I might have to beg your help again !!!! <img src="/ubbthreads/images/graemlins/blush.gif" alt="" />

Unless your company does hosting for it's business stuff like DNS and webservers don't usually need to be touched much once they are set up and running. In fact a lot of unix servers don't need to be touched very much apart from patching/upgrades once they are set up properly.

If you do need to add things like new VirtualHosts or DNS zones it's worth writing a script, that way you only need to work out how to do it once, you test it thoroughly and reduce the risk of human error in future setups - and you don;t need to stress your memory nearly so much.

In fact I recommend scripting as much of the routine and semi routine tasks as possible.
If you do something more than about 3 times, write a script.
It increases quality by reducing the scope for human error and the foibles of human memory.
And once your script is robust enough you can put a web front end on it and then other people who have no idea about unix can start perform the task. E.g. you can delegate tasks to the helpdesk or the developers or whatever.
You still need to learn how to do whatever it is you need to do the first time, but after that you have all the steps outlined for you in the script so you don't have to remember as much of the fine details (.e.g exactly which options.flags you need to use etc) and you can be more sure you won't forget a step etc, because it is all there in the script.

Also check out the script command - it records a shell session for you so when you are trying to work something out you can go back and look over exactly what it is you did to get where you are.

I've PM'd you my email address - if you need some help Unix generally or scripting feel free to email me - I've been sys admining linux and a bit of Solaris for more than 10 years so if you get stuck I may be able to help you out or at least point you in the right direction.
But I'll cop out right now and say I know very little about admining SVN, CVS and git.

I have more problems than not looking around BF. don't know if i wanna pay any longer either

Thanks for the offer to tap your experience. I replied with some specifics, but you're right -- for the most part things are stable. My boss is currently working on a more robust content management system for the Internet Services folks, who are the source of much of the support work.

Additionally, plans are to move most (perhaps even all) of the Unix server tasks we've been doing in-house (Web servers and internal/external DNS) to a hosting company. We've evolved into more of a Microsoft shop and the volume of web traffic we handle doesn't really warrant owning multiple racks of servers we've purchased, pay maintenance on, and have to replace periodically. We'll get better power and connectivity redundancy through a hosting company than we've ever had on site and can adjust bandwidth to our actual needs rather than having to buy year-round based on our peak seasonal requirements.

While I expect that the Unix support to be a pain in the short-term, it should decrease as we implement the new CMS and hosting plans. Finally, if something neither I nor my boss can handle occurs, I've been told that we can get consultant $ for specific incidents (but not long term -- our Unix admin was an on-site contractor for over two years), so I should be OK.