Slashdot Mirror


Why Do We Name Servers the Way We Do?

jfruhlinger writes "If you use a Unix machine, it probably has a funny name. And if you work in an environment where there are multiple Unix machines, they probably have funny names that are variations on a theme. No, you're not the only one! This article explores the phenomenon, showing that even the CIA uses a whimsical server naming scheme." What are some of your best (worst?) naming schemes?

94 of 1,397 comments (clear)

  1. Slashdot by daybot · · Score: 5, Funny

    h t t p colon slash slash slash dot dot org

    1. Re:Slashdot by jellomizer · · Score: 3, Interesting

      Well I think the reason for having a bunch of "Cute" names for the server is just really prevent confusion.
      Oh Crap Medusa is down. vs. WebServer014 is down. We tend to relate better with recognizable names, so it creates a spot in the persons memory of all the systems, vs boring names where they will just become mixed in the fray.

      In college over a decade ago, we had Greek Mythogy Names. And I still know what system is which by the name.
      Morpheous and Ultra Sparc was the main file/web server
      Zeus a 2 CPU ultra Sparc e250 was the remotelogin ssh/telnet server where the CS students did their work.
      Then we had Valhalla and Pandora the Ultra Sparc 1 workstations...

      It is actually quite effective memory tool. for the NT workstations we just had NT1 NT2.... I can't remember what order they were in or which one was different then the other.

      Those names actually made administration much easier.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Slashdot by mrbooze · · Score: 5, Insightful

      I've mostly found it a sign of a company's size/age/maturity as to how boring the server names are. Several places I've worked for started out with the admins coming up with their funny/cute/dorky naming schemes, only to eventually have server names be locked down in the name of STANDARDIZATION.

      Then you have endless meetings to decide what should be the important components of a system name. Should it indicate the machine's location? It's OS? It's function? Should it even indicate which rack number and elevation slot the system is in? Eventually you end up with racks full of servers named SJC-LX-APPDEV01, NYC-SV-EXCHG02, and LDN-UX-SMTPDR01.

      I have to admit, a little part of me misses having room for a little creativity in naming systems, but then the rest of me doesn't miss wasting time trying to come up with names for work systems. I've always got my home network to label with my ever-changing nerdly obsessions.

    3. Re:Slashdot by jaxtherat · · Score: 5, Insightful

      It does not bloody well make administration easier! If you have say X servers scattered over Y locations, it makes sense to call them:

      (site)(os)(function)(number)

      i.e.

      sydwindb002

      meaning sydney windows database 002

      as opposed to tauron or frickin picon, or smurf (I'm not kidding you). Best of all though I've seen was server. Just server.

      Serving what?? This was in a rack of 27 severs in total.

      As a sysad, it shits me when people come up with 'cute' nonsensical names that have no consistency and aren't self explanatory. I mean, good software engineering principles dictate that you use meaningful variable names. Why not server names as well?

      --
      http://www.zombieapocalypse.tv/
    4. Re:Slashdot by linhares · · Score: 4, Funny

      Jenna Jameson Briana Banks Devon Tera Patrick Stormy Daniels Silvia Saint Janine Lindemulder Crissy Moran Jesse Jane Gauge Krystal Steal Nicole Sheridan Tawny Roberts Mercedez Amber Michaels Brittney Skye Catalina Cruz Miko Lee Veronica Zemanova Houston Lanni Barbie Shyla Stylez Racquel Darrian Teagan Presley Mindy Vega Alicia Rhodes Rita Faltoyano Adele Stephens Susana Spears Aria Giovanni Kobe Tai Erica Campbell Gina Lynn Kelly Madison Eva Angelina Adriana Sage Jill Kelly Sky Lopez Puma Swede Chloe Jones Jasmin St. Claire Anita Dark Nikki Nova Terri Summers Belladonna SaRenna Lee Jana Cova Carmen Luvana Jenna Haze Danni Ashe Anetta Keys Sydney Moon Lisa Sparxxx Zdenka Podkapova Sydnee Steele Kyla Cole Taylor Rain Alaura Eden Asia Carrera Gina Ryder Devinn Lane Sophie Sweet Kim Chambers Jodie Moore Alexis Amore Bobbi Eden Rachel Aziani Raylene Aimee Sweet Katsumi Stephanie Swift Brandi Lyons Lovette Amy Reid Lonnie Waters Jewel De' Nyle Angelica Sin Alexa Rae Aurora Snow Tanya Danielle Sandra Shine Avy Scott Tiffany Mynx Cherokee Pantera Tabitha Stern Chloe Dior Ava Devine Dasha Isabella Camille Niki Blond Daniella Rush Kelle Marie Ashton Moore Charmane Star Allysin Chaynes Courtney Cummz Katja Kassin Shay Sweet Penny Flame

    5. Re:Slashdot by fm6 · · Score: 3, Insightful

      You're quite right, and not just about servers. I've been at companies where every printer had its own cute name. And these weren't small companies with a couple of printers, we're talking dozens of them. A real nuisance when your regular printer is broken and you can't remember the name of one of the alternates.

      I came back to work at one of these companies, and now all the printers have boring names based on where they are. Makes life much easier.

    6. Re:Slashdot by netcrusher88 · · Score: 4, Informative

      I personally hate that naming scheme, it's confusing and produces long, hard to remember and typo-prone hostnames.

      NS records exist for a reason. Your example could just as easily be:

      windb002.syd

      Since every Windows network (and that tends to be where I see domain names like that) is a real DNS domain, there's no reason you couldn't do this. This has the added benefit of being able to push a DNS search domain based on the location of the computer doing the DHCP request, then having certain hosts that are replicated in each area subdomain, for example a CMS or a DB. Does sydwindb002 replicate to nycwindb002? Have windb002.syd replicate to windb002.nyc (and vice versa) then let users just put in windb002, and traveling users will be able to automagically use the closest and probably fastest DB server.

      Or, in the case of a CMS, have one top-level CMS that refers to local ones. Say you have cms.example.com and cms.xxx.example.com. Depending on your network location, typing in CMS will either take you to the top-level CMS or the local one, which might aggregate data from the top-level one.

      --
      There's an old saying that says pretty much whatever you want it to.
    7. Re:Slashdot by Jurily · · Score: 5, Funny

      OMG, I just found my new naming convention. Thank you soooooo much! Brilliant, just freaking brilliant.

      Please don't. Unless you want your boxes to go down a lot.

    8. Re:Slashdot by DriveMelter · · Score: 5, Informative

      I thought this was a good idea until the first time we moved an office...

    9. Re:Slashdot by seanellis · · Score: 3, Funny

      Got to be careful with this. It only takes an extension and a few more meeting rooms before you are asking people to meet in the Cradle of Filth.

  2. Snow White Theme by Anonymous Coward · · Score: 5, Funny

    Old Reader's Digest Joke:

    Seven terminals named Doc, Happy, Sleepy, Grumpy, . . ., and a printer named "Handsome Prints". :-)

  3. Well, I'm currently using Fwiffo. by Rei · · Score: 3, Funny

    My main server (which used to break all the time) is named Ultron, while various other computers and printers on the network have names such as Zebranki, Greenish, and Spathi.

    --
    Nothing says 'welcome to the neighborhood' like a gunny sack full of dead squirrels.
    1. Re:Well, I'm currently using Fwiffo. by TheRealMindChild · · Score: 5, Interesting

      See, I don't get it. WHY would you name your servers this? If you smack your head or have a hard night drinking, would you know FOR SURE that ServerX is the file server or the database server? Would you code like that? At least make the names useful.

      Personally, I like MrDomainController, MrNameServer, MrFileServer, etc. Have a backup? Meet MsDomainController. Need yet another backup? JrDomainController? Need another one? No you don't. See, easy, unambiguous, useful.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    2. Re:Well, I'm currently using Fwiffo. by sr180 · · Score: 4, Insightful

      We had this exact problem. Originally they were all named Webserver1,Webserver2,Monitoring1,Monitoring2 etc etc etc. We decided it would be cool to name them all after simpsons characters. 3 Days later I get an alert to my phone at 2am to tell me Nelson is not responding to ping. WTF is Nelson? Is he important? No idea what he did, and if he needed rebooting immediately or could wait till reasonable hours.

      Hence I'm a big proponent for a useful naming scheme.

      --
      In Soviet Russia the insensitive clod is YOU!
    3. Re:Well, I'm currently using Fwiffo. by Anonymous Coward · · Score: 3, Funny

      No it's not! He took his data and (parts of) his applications' settings with him each time I would guess.

      So it's more like extracting his old girlfriend's brain and stuffing it in his new girlfriend's head. ... and _then_ calling her by the old girlfriend's name.

    4. Re:Well, I'm currently using Fwiffo. by russotto · · Score: 4, Funny

      OR, intentionally getting a new girlfriend with the same name as the last one ;)

      Saves a fortune in tattoo removal.

    5. Re:Well, I'm currently using Fwiffo. by darkpixel2k · · Score: 3, Insightful

      We had this exact problem. Originally they were all named Webserver1,Webserver2,Monitoring1,Monitoring2 etc etc etc. We decided it would be cool to name them all after simpsons characters. 3 Days later I get an alert to my phone at 2am to tell me Nelson is not responding to ping. WTF is Nelson? Is he important? No idea what he did, and if he needed rebooting immediately or could wait till reasonable hours.

      Hence I'm a big proponent for a useful naming scheme.

      Yeah--that's even been a problem at the company I work for. Several times per week I end up in a conversation like this:

      Me: "I can't connect to 192.168.7.241--it's out of admin slots for remote desktop" Boss: "What's 192.168.7.241? Is that DumbServerName1?" Me: "I'm not sure, what's 'DumbServerName1'?" Boss: 'It's the domain controller." Me: "Great, that still doesn't help."

      I usually know everything by IP or it's DNS name. Where 192.168.7.241 might be 'mail.somedomain.com' but the box has a hostname of DumbServerName1

      Lame.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    6. Re:Well, I'm currently using Fwiffo. by rvqbl · · Score: 3, Funny

      Speaking of breaking all the time, a friend named a mainframe Linda Lovelace because it sucked so much and went down on you all the time...

    7. Re:Well, I'm currently using Fwiffo. by Spatial · · Score: 4, Funny

      Nelson is not responding to ping

      *Points* Haaa-haaa.

    8. Re:Well, I'm currently using Fwiffo. by Gumbercules!! · · Score: 4, Interesting

      This is why my mail server is 192.168.1.25 and the web server is 192.168.1.80, etc. Dev web server is 192.168.1.81. At least you can guess by the IP what it's about, based on that scheme.

      Oh and their names?
      Moiraine
      Berelain
      etc...

    9. Re:Well, I'm currently using Fwiffo. by rdebath · · Score: 4, Funny

      No that should be Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus, Zathrus and Zathrus.

      Oops, sorry, Zathrus isn't there any more.

  4. D-d-d-dupe by pwnies · · Score: 5, Funny

    I like that in this edition of Duplicate Stories on /. Monthly, the link in the story actually links back to a previous story that's asking the same thing! Thanks for saving us the few seconds of searching for the older stories on this one /.!

  5. Wines, cheeses, trees by radixzer0 · · Score: 5, Insightful

    A goofy naming scheme is a bad idea when you're running over 100 servers in a dynamic environment. When your servers are named after wines, cheeses, and trees, who can say what Oak does, or Chablis, or Feta, or Jujuba, or Sassafras, ad nauseum.

    -r0

    1. Re:Wines, cheeses, trees by Rei · · Score: 5, Funny

      Well, not sure about where you are, but around here, adnauseum is the mail server.

      --
      Nothing says 'welcome to the neighborhood' like a gunny sack full of dead squirrels.
    2. Re:Wines, cheeses, trees by snowgirl · · Score: 3, Insightful

      A goofy naming scheme is a bad idea when you're running over 100 servers in a dynamic environment. When your servers are named after wines, cheeses, and trees, who can say what Oak does, or Chablis, or Feta, or Jujuba, or Sassafras, ad nauseum.

      Well, the wines are build servers, the cheeses are webserver backends, and the trees are infrastructures... lol, sorry, being a bitch is so fun sometimes.

      I did work at a job where we used acronyms to know what the computer was assigned for, but once you got past all of that, there was just a number for your team, and project. "Uh... which computer builds the x86fre version? 6? Oh, ok..." It required a map that was not just computer readable, but human readable.

      Usually, it just ended up being team-specific knowledge that no one else knew. It was easy enough to know the prefix down to your stuff, it was regular, which just required a simple arbitrary map of numbers to purpose... what would be the difference between that and cheeses, wines, or trees?

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    3. Re:Wines, cheeses, trees by repvik · · Score: 5, Insightful

      Duh, you don't refer to the servers by name directly, it's just a name.
      Use CNAME with functionality pointing to that server. Naming a server "www" is just silly when it also does other stuff.
      Naming the server "Hezbollah" and having a bunch of cnames point to it ensures you can easily move a service at any later time without having to rename the server.

    4. Re:Wines, cheeses, trees by ushering05401 · · Score: 4, Funny

      If obscurity is not a chief objective you could latinize the server's functions. Mailicus, Proxius, Validicus etc..

      Add in some major/minor modifiers and you are in business.

    5. Re:Wines, cheeses, trees by Paua+Fritter · · Score: 4, Insightful

      Quite correct - someone please mod this up. The extra layer of abstraction you get by using CNAME records in your DNS really helps. A server's "real" name should not be the name of it's functional role.

    6. Re:Wines, cheeses, trees by revlayle · · Score: 4, Interesting

      We never use standard names, our company deals with lots of e-payments and the idea is that the less obvious our naming scheme is, the more difficult it is for hacker to really figure out what the purpose of a server is and what it may store.

      A little extra work for us, but we have ways internally of handling this issue without much headache.

    7. Re:Wines, cheeses, trees by vux984 · · Score: 5, Funny

      A little extra work for us, but we have ways internally of handling this issue without much headache.

      If your going for obscurity I'd go the other way... give some old pentium 1 with a copy of tradewars2000 in a closet the name 'auth-pay-master', and the your main server something like 'help-desk-print-server' ;)

    8. Re:Wines, cheeses, trees by darkpixel2k · · Score: 3, Insightful

      Quite correct - someone please mod this up. The extra layer of abstraction you get by using CNAME records in your DNS really helps. A server's "real" name should not be the name of it's functional role.

      Pretend for just one moment that your network guy got clocked by a bus. He won't be back to work until someone figures out a way to raise the dead.

      You're the new guy they just hired to replace him. Who cares about CNAMEs when you're on the server looking at the hostname? Someone tells you 'daffy' and 'kirk' are down. What are they? What do they do?

      On the other hand, if I told you 'mx2' and 'nas1' are down, you have a better idea of what you're dealing with... Forget that there's a CNAME from mail to daffy and a CNAME from p0rnserver to nas1.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    9. Re:Wines, cheeses, trees by gardyloo · · Score: 5, Funny

      Naming the server "Hezbollah" and having a bunch of cnames point to it ensures you can easily move a service at any later time without having to rename the server.

            Right. It also means that if there's a horrible disk crash, the FBI and NSA no doubt have several nice backup copies from last Friday you can borrow.

    10. Re:Wines, cheeses, trees by betterunixthanunix · · Score: 3, Funny

      Personally, I prefer to name my servers after women I have been...involved...with. This easily covers hundreds of systems.

      --
      Palm trees and 8
    11. Re:Wines, cheeses, trees by BluBrick · · Score: 5, Funny

      So that'd be virtual machines, then?

      --
      Ahh - My eye!
      The doctor said I'm not supposed to get Slashdot in it!
    12. Re:Wines, cheeses, trees by Tassach · · Score: 3, Insightful
      Security through obscurity is never an effective strategy. Anyone talented enough to breach a properly administered firewall and gain access to your internal network is going to be slowed down for all of five minutes by your obscure naming scheme.

      Conversely, your admins are going to take a productivity hit every time they have to do anything to more than one box. Even a small headache gets annoying when you have to deal with it multiple times every day.

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    13. Re:Wines, cheeses, trees by syousef · · Score: 5, Insightful

      On the other hand, if I told you 'mx2' and 'nas1' are down, you have a better idea of what you're dealing with... Forget that there's a CNAME from mail to daffy and a CNAME from p0rnserver to nas1.

      Until someone decides to retire mx2, move functionality from nas1 to a new server named nas2, and make use of the old mx2 as the mail server.

      Now you have nas1 and nas2. One's a mail server. You get to guess which one. But hey if you think you REALLY know better than the RFC, it's your network to run.

      --
      These posts express my own personal views, not those of my employer
    14. Re:Wines, cheeses, trees by ogdenk · · Score: 3, Insightful

      1.) Use TXT records in the DNS to give people who come behind you a clue.

      2.) The first thing you should be doing when you get a new network admin position is digging around in the DNS server a bit to get the lay of the land and pay attention to CNAME records.

      3.) The next thing I usually do is run nmap on the subnet to see what's open where.

      4.) Usually someone will have at least a slight clue. Usually.... Ask around.

      5.) If the dude wasn't a complete incompetent dumbass, he would have left some documentation. I document my networks extremely thoroughly and have an NMS set up which will have extensive text information on hosts as well. I also make sure a couple of key personnel have passwords to the NMS. I even have a binder labeled in big letters with a sharpie on the bookshelf "READ ME IF KEVIN DIES IN TRAGIC CAR ACCIDENT". Not kidding.

      If you don't have thorough documentation, this is not a form of job security. You are not special. Someone can and will ensure they survive without you. Or they'll simply reinvent the wheel. All you're doing is being a dick to your fellow IT brethren.

      If all of the above fail, chances are you'll need to recreate the network in your own image anyway. They don't teach how to write good documentation in MCSE study guides. There's a reason I refer to the MCSE cert as "Must Call Somebody Experienced".

  6. Rebel by Dyinobal · · Score: 5, Insightful

    Naming our machines in odd and amusing ways it our way of secretly rebelling against over management.

    1. Re:Rebel by WillAffleckUW · · Score: 4, Interesting

      mod this one up!

      I remember the first computer I networked I changed so it showed up as H3110 (Hello) ... since they insisted on numbers.

      --
      -- Tigger warning: This post may contain tiggers! --
  7. mac addresses by Anonymous Coward · · Score: 5, Funny

    I name each of my servers the name of another computer's mac address on the network. This way, as part of my retirement package I'll have the joyous knowledge that the person who takes over my position is going insane.

  8. Worst naming scheme: by El_Muerte_TDS · · Score: 4, Interesting

    functional naming.

    Machines need arbitrary names, functional names are aliases.

    1. Re:Worst naming scheme: by the+white+plague · · Score: 5, Funny

      It gives your customers something to chuckle over during traceroutes too. Why settle for letting them discover they traversed v11s0p1.dal01.blahblahblah.net, when you could let them know that they went through thebeast.bbb.net or ratbastard.wehateourjobs.com?

  9. Porn stars by Anonymous Coward · · Score: 5, Funny

    I used to run a fairly lucrative business at a time when a certain industry was much more profitable... JennaJameson would always go down while RonJeremy would always be up.

    Coincidence? I think not.

  10. Break it down by DigiShaman · · Score: 4, Interesting

    Use this convention for naming servers. company - airport code - role. For example, MSFT-PDX-MAIL01 (or DC01, TS01, APP01, etc)

    --
    Life is not for the lazy.
    1. Re:Break it down by initialE · · Score: 5, Interesting

      And a server that serves more than 1 role? or if you're trying to fit names into a small namespace? Or you ever have to pass the name over the phone to a colleague?

      --
      Starbucks, Harbuckle of Breath.
  11. Snow by snowgirl · · Score: 4, Insightful

    Just like my user name, I decided to go with the word "snow" in various languages. So far, I have my router chioni, server nix, desktop losse, and various other names for components. My wii is yuki, my xbox 360 is xue, my ipod touch is lumi. Beyond that I've also used "eira" and "schnee".

    At my university NMSU, the CS department used alcoholic drinks (vodka, gin, etc), which were changed to vehicles (cobra, stingray) over complaints from an incoming professor. The sunrays were "bear" in various languages (oso, medved, ursa), and later they had words from the hacker's dictionary (foo, bar, baz, frob)

    The naming schemes all were easily memorable, and prompted word associations, making them easy to mentally group. Ok, except the translations for bears, (and mine for snow) except for fellow crazy polyglots, and linguiphiles.

    --
    WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    1. Re:Snow by adnonsense · · Score: 4, Funny

      If your wii is yuki, you might want to see a doctor!

  12. Never owned a server, but... by greenguy · · Score: 4, Funny

    I had a series of Macs before I became a diehard Linux guy. I didn't know I could name the first one, but then came Mac and Cheese, Mac Truck and Fanfare for the Common Mac (around the time of Copeland).

    Why? Because I could.

    --
    What if I do the same thing, and I do get different results?
  13. My nonsensical method by fuelvolts · · Score: 3, Funny

    I name my PCs/Servers by the core name of the CPU:
    My desktop is "Agena" (Phenom X4)
    Laptop is "Trinidad" (Turion X2)
    Wife's Laptop is "Merom" (Celly)
    File Server is "Sparta" (AM2 Sempron)


    I've been doing this for years and it's a built in reminder that I need to upgrade whenever I connect to another machine. ;)

  14. Logical names fail eventually by rossz · · Score: 5, Insightful

    Over time, systems get refactored for uses that they were not originally intended, so that box named web1 is now an ftp server and nobody bothered to rename it. The same happens when you try to name them by physical location. r1a2r10n5 got moved from Room 1, Aisle 2, Rack 10, Number 5 to another room entirely.

    The easiest time I had dealig with servers was when they were named after japanese monsters. We had Godzilla, Mothra, etc. We all know that Godzilla was the PostresSQL server. If a box's purpose changed, we didn't have to worry about renaming it and people would eventually learn its new purpose.

    Whimsical names work.

    --
    -- Will program for bandwidth
  15. JPMorgan's servers named after Dead Utopians by itsybitsy · · Score: 3, Interesting

    One group at JPMorgan had unix boxes named "Marx" (yes after Carl Marx) and "Bucky" (yes after Buckminster Fuller), and a slew of other Dead Utopian Philosophers.

    Naturally the program that the group developed (in Visual Works Smalltalk with the Gemstone Object Database) for Trading Hybrid Derivatives is known as "Das Kapital"! Yes, it also has a start up screen with a picture of good old Carl Marx. This program trades and manages Trillions of Dollars of value (although the total value dropped recently due to, well, you know). But, was this program was likely part of the problem? Who knows? ;--)

  16. Apparently odd naming often has a purpose by jmorris42 · · Score: 3, Insightful

    Odd named hosts often have a meaning once you are clued in on the naming scheme. First off it really helps to give hosts on the network a NAME not just a number. You could just skip DNS if you are going to number em. A well thought out naming scheme helps. If you do it right the name gives you a rough idea what it does and still allows some fun in naming.

    If I see a tree themed hostname I instantly know it is one of the machines in a patron lab. Flowers are staff hosts and mythological beings are in the server room. Yes machines in a lab could just be numbered but ya could also name yer cats Cat 1, Cat 2, Cat 3, etc.

    --
    Democrat delenda est
    1. Re:Apparently odd naming often has a purpose by FuzzyPlushroom · · Score: 5, Funny

      ...and logically, Cats 5 and 6 would be very similar in appearance, but Cat 6 would end up able to chase mice ten times faster.

  17. Surnames by jrothwell97 · · Score: 4, Funny

    All my computers are named after famous computerists. For example, Welchman. Turing. Babbage. (The exception is my old laptop, named after Richard Hammond.)

    My phones are also given surnames: Stubblefield, Adams, etc.

    All my iPods are called Steve.

    --
    Those using pirated Tinysoft signatures(TM) are a real threat to society and should all be thrown in jail.
  18. Re:Artificial Intelligences by Anonymous Coward · · Score: 5, Funny

    ...but I later decided on naming them after AIs.

    Roker?
    Jolsen?
    Sharpton?
    Yankovic?
    Gore?

    Oh, wait...

  19. Lots of good ones on Stack Overflow by Chad+Birch · · Score: 5, Informative

    There's a pretty sizeable collection of funny/clever server names on Stack Overflow here:
    http://stackoverflow.com/questions/262657/the-coolest-server-names

    --
    Sturgeon was an optimist.
  20. You name them after computer parts by kcbanner · · Score: 5, Funny

    So when something goes wrong, people sound like morons: "Why is motherboard down!?" "I can't connect to RAM!"

    --
    Obligatory blog plug: http://www.caseybanner.ca/
  21. "Goofy" naming scheme? by mangu · · Score: 5, Funny

    Great idea! Let's name the others "Mickey", "Minnie", and "Pluto"

    1. Re:"Goofy" naming scheme? by mangu · · Score: 5, Funny

      Pluto -> "Saturn", "Mars", "Tellus", "Uranus"
        What's the next series?

      "Urballs", "Urpenis", "Urnavel"...

  22. Whimsical Conference room names by bwhaley · · Score: 4, Funny

    Ok, this drives me nuts. It's a little off topic, since it's names of conference rooms instead of server names, but the concept is the same.

    Here in Colorado, we have 54 mountain peaks that are > 14,000 feet. They're referred to as "fourteeners," and they all (of course) have names.

    Every company in Denver thinks they're damn clever by naming their conference rooms after the fourteeners. I don't know how many Long's Peak and Mount Evans conference rooms I've sat in, but it makes me want to hurl my chair at the window.

    Ok, time for my anger management class. =p

    --
    "I either want less corruption, or more chance
    to participate in it." -- Ashleigh Brilliant
  23. Re:naming by tsa · · Score: 4, Funny

    ...and period3 means that you're 12 years old and just started puberty?

    --

    -- Cheers!

  24. Why? Because we can! by WillAffleckUW · · Score: 3, Interesting

    And we name our Win boxen silly names too - every Linux or Unix or Windows box in my lab is named after a local animal (Linux or Unix) or local plant (Windows).

    It's the same reason that people have nicknames for their campers and their houses ... or the CIA is named Foggy Bottom.

    --
    -- Tigger warning: This post may contain tiggers! --
  25. I know a name for itworlds new mysql server by kcbanner · · Score: 4, Funny

    "slashdotted". In memory of what happened to the old one.

    --
    Obligatory blog plug: http://www.caseybanner.ca/
  26. Pants are down by JungleBoy · · Score: 4, Funny

    Our usenet upstream provider used to call their main server Pants. Their admin said, "If pants is down, we're fucked."

    --
    "You never know when some crazed rodent with cold feet might be running loose in your pants."
    -Calvin
  27. from rfc2100 by nemo · · Score: 4, Interesting

    (ftp://ftp.isi.edu/in-notes/rfc2100.txt)

    The Naming of Hosts is a difficult matter,
                    It isn't just one of your holiday games;
            You may think at first I'm as mad as a hatter
                    When I tell you, a host must have THREE DIFFERENT NAMES.

            First of all, there's the name that the users use daily,
                    Such as venus, athena, and cisco, and ames,
            Such as titan or sirius, hobbes or europa--
                    All of them sensible everyday names.

            There are fancier names if you think they sound sweeter,
                    Some for the web pages, some for the flames:
            Such as mercury, phoenix, orion, and charon--
                    But all of them sensible everyday names.

            But I tell you, a host needs a name that's particular,
                    A name that's peculiar, and more dignified,
            Else how can it keep its home page perpendicular,
                    And spread out its data, send pages world wide?

            Of names of this kind, I can give you a quorum,
                    Like lothlorien, pothole, or kobyashi-maru,
            Such as pearly-gates.vatican, or else diplomatic-
                    Names that never belong to more than one host.

            But above and beyond there's still one name left over,
                    And that is the name that you never will guess;
            The name that no human research can discover--
                    But THE NAMESERVER KNOWS, and will us'ually confess.

            When you notice a client in rapt meditation,
                    The reason, I tell you, is always the same:
            The code is engaged in a deep consultation
                    On the address, the address, the address of its name:

                                    It's ineffable,
                                    effable,
                                    Effanineffable,
                                    Deep and inscrutable,
                                    singular
                                    Name.

  28. Re:Idiots... by allauthors · · Score: 3, Insightful
    The difference, is that while the total_annual_cost variable should and will never hold anything other than the "total annual cost", HappyZippers may eventually be re-purposed to something other than what it is currently used for; this is a normal and natural evolution of server function in the sysadmin world, but it is useful to have a tag which sticks to that particular piece of hardware, regardless of where it moves.

    And for the same reason that we name the variable total_annual_cost instead of c113, it helps to have a human-readable/remember-able name for the server instead of a collection of gibberish which, though it may translate eventually into some useful information, is so hard to remember that it takes longer than just looking it up on the chart of server names on the wall. The names must be arbitrary because the server must be able to be repurposed, but the names must be consistent or they do not offer any mnemonic assistance.

    We name servers for one group out of one arbitrary category (say mythical monsters) and servers for another group out of another (say SF authors). This allows the name to communicate some information directly (info which is unlikely to change even if the server's role is changed within that group). While all other information can quickly be found on the wiki or a printed out chart, which actually happens faster than deciphering that at13g3d12 is the 12th dev server for group 3 in the at&t datacenter rack 13. (It really is faster to look it up than to decode even that simple of an encoded name.) Finally, for an individual dev working on several projects it is much easier to remember that the billing project is on mothra while the reporting project is on grendel than it is to remember that one is on at13g3d3 and one is on at13g3d4.

    My company actually switched from an arbitrary but consistent naming convention to a strictly encoded naming convention and quickly switched back when the loss of efficiency and productivity was actually measurable.

  29. Futurama Naming Scheme by dominator · · Score: 3, Funny

    My laptop: Fry
    Wife's: Leela
    Wife's old laptop: Amy
    Printer: Zoidberg (dispenses ink)
    Router: Bender ("bends" packets)
    OLPC XO Laptop: Kiff (both small and green)
    Car: Planet Express Ship (with which the 2006 Honda Civic shares a striking resemblance)
    Cat: Zapp (cavalier, not too bright, doesn't wear pants).

    I've been told by wifie that future pet names will include "Nibbler" and "Scruffy".

  30. Re:The Simpsons by PPH · · Score: 5, Funny

    We had a Simpsons fan where I used to work, When our engineering groups got our first workstations, he named his 'homer' and suggested that we follow suit. We named ours 'ulysses'.

    --
    Have gnu, will travel.
  31. I've got a system by Rhapsody+Scarlet · · Score: 3, Interesting

    My PCs are all named after Studio Ghibli heroines. I first used this with San (retroactively naming her predecessors Ichi and Ni), then with Chihiro and now with Shizuku. Both of the last two are still operating, and will be replaced with Haru and Taeko respectively. This doesn't factor much into operations, though the command line does display "rhapsody@shizuku" on this PC.

  32. Re:Idiots... by clambake · · Score: 4, Insightful

    By your logic, I can name all the variables in my code "x", "y", and "z" and then complain that they've hired *idiots* who can't remember that "x means the number of items in the shopping cart, duh". I could claim it's just a rite of passage into the world of complex software development...

  33. Re:Idiots... by hobo+sapiens · · Score: 4, Insightful

    Depends. Functional naming conventions often try to name servers according to some crazy attempt to fully qualify the server name. It'd be like naming your variables like I have seen in some VB programs (stupid Hungarian notation!)

    I have worked in places where servers are given functional names, and places where servers are named in a more whimsical fashion. Functional names suck.

    Even "meaningful" names lose meaning over time, due to changes in naming conventions, repurposing of hardware, or other unforeseen things. Might as well give them whimsical names which relate to one another, yet aren't dependent on the implementation details. Servers are named for human reference, else they'd be IP addresses.

    Then, a new director or new group handles server allocation. The naming convention changes and you have to remember yet another arcane naming system.

    Again, functional names are cumbersome and hard to remember. And you often have to type server names over and over again. It's easier to remember names like sleepy, grumpy, and dopey than to remember and constantly retype TXDALDC09DEV01, TXDALDC03DEVDB01, and CASFDC06QADB11.

    If you just hate whimsical names, then at least serialize the server names. Server01, Server02, and Server03 is a better way to go than coming up with some complex system of fully qualified names.

    --
    blah blah blah
  34. Yay for colours! by adamkennedy · · Score: 5, Interesting

    For smaller setups with less than ten machines, I like to use colours.

    Red - Production Server
    Orange - Staging Server
    Yellow - Test Server
    Green - Dev Server
    Blue/Purple/etc etc for other things like the database server etc.

    This way, when I'm setting up PuTTY or another shell, I can set the foreground text colour for each machine to match the server name, which stops most of those embarrassing mistakes when you run a command on production that you meant to run on test, and so on.

    1. Re:Yay for colours! by Dzimas · · Score: 3, Funny

      I rue the day a colorblind co-worker unwittingly annihilates your production server. :)

  35. Let's just say the Dallas server... by randmcnatt · · Score: 5, Funny

    ...was named "Debbie"

  36. Man-made disasters by GuruBuckaroo · · Score: 3, Funny

    ThreeMile, Valdez, Congress, HyattKC, PruitIgoe (ok, a little local, look it up). Damn, there were more, but I can't remember them anymore.

    --
    Poor means hoping the toothache goes away.
  37. Borg by EmperorOfCanada · · Score: 3, Interesting

    In Halifax some years ago a larger University took over a smaller but much better Engineering school called TUNS. The takeover was quite hostile with Dalhousie doing a "My way or the Highway" routine in all areas. The computer system set up by Dalhousie for TUNS was called borg. Never has a better name been given to a server.

  38. Re:Server names by russotto · · Score: 5, Funny

    my laptop is Ockham.

    Thus, if you tether your Motorola cell phone to your laptop, you end up with Ockham's RAZR.

  39. Re:Periodic Table by jhealy1024 · · Score: 3, Funny

    Don't forget the most important part: the host part of the IP address should be the element's atomic number (e.g., "Einsteinium" -> 192.168.0.99).

  40. Whoops by ammaro · · Score: 5, Funny

    We reused an old piece of junk machine as a print server in our development lab, which was connected to the enterprise network. We gave it an appropriately descriptive name, Dungpile. Little did we know that in its prior life Dungpile had been configured as a DHCP server. (We didn't look at it too closely... our bad.) One day we hear a frazzled guy from the IT department going door to door crying, "I'm looking for Dungpile! Does anyone know where Dungpile is?" It turns out the enterprise DHCP server had a hiccup, and in the subsequent negotiation for which backup would take over, Dungpile won out. Our little print server started handing out 10.10.*.* IP addresses (it was evidently set up for a private network) to the enterprise workstations. That worked very poorly. The IT folks could tell the bogus addresses were coming from a machine called Dungpile, but didn't know where it was located. (I don't know why they didn't just boot Dungpile and force their primary server to resume duties. The weren't a great team.) Anyway, it made my day hearing someone wandering the hall yelling about finding dungpile.

  41. Why... by LaskoVortex · · Score: 3, Interesting

    People name computers because it makes good sense. Although computers don't have self-awareness and thus intrinsic personalities, they are subject to the natural tendency for people to project personalities on them based on behavior and appearance. People who don't project personality onto other objects and people probably have a personality disorders themselves, like Asperger's syndrome. But the projection of personality by humans is a mnemonic that aides in remembering a particular blend of traits of a person (or other object) and is thus a practical habit. People name a machine to make a slot in their memory for its personality and then fill in that slot as they learn about their machine. In this sense, systematic names like server01, server02, server03, etc., are not unique enough to be helpful because they can not easily be differentiated by the normal person.

    --
    Just callin' it like I see it.
    1. Re:Why... by fm6 · · Score: 4, Insightful

      God save us from armchair psychologists!

      Although it may be healthy to project personalities onto things (I'm a little skeptical, though I could maybe be persuaded by somebody who doesn't go around making sweeping psychiatric diagnoses of people he's never met) that hardly justifies encoding those projections into names. I'm not saying you should never do it (in fact, I do it a lot) but when you do it, be practical. Others may not share your projections. They may find your names confusing, misleading, or even offensive.

      Where I work, there are two products that are very similar, but not quite. Somebody in engineering decided that their internal code names should be after a comic book hero and his evil twin. Those of us who don't follow comic books don't find these names very mnemonic, and often get them confused.

      You're wondering why I don't tell you these two comic book characters. Can't, because they're for internal use only. If it became widely known that these products had these code names, somebody with a similar product with a similar name could sue us for trademark infringement. (The official product names combine trademarks we've already established with meaningless strings of letters and numbers.) That's another problem with these cute names: get careless and you get sued. Apple actually spends a lot of money paying off people with claims against the names they use for all their OS updates. Possibly worth it, since it contributes to their main marketing asset: their coolness factor. But not worth it for most companies.

      And then there are names that just carry the cute reference bit too far. I mean, come on, whose idea was it to name a Linux distro "Yggdrasil"?

    2. Re:Why... by poopdeville · · Score: 5, Insightful

      Although it may be healthy to project personalities onto things (I'm a little skeptical, though I could maybe be persuaded by somebody who doesn't go around making sweeping psychiatric diagnoses of people he's never met) that hardly justifies encoding those projections into names.

      There's a simple, practical reason for using names: IP addresses can be hard to remember.
      There's a simple, practical reason for using "themed" name spaces: coming up with dozens/hundreds of names can be hard.

      --
      After all, I am strangely colored.
    3. Re:Why... by LaskoVortex · · Score: 3, Funny

      I'd argue with you because it seems like you are arguing, but I can't really pinpoint your thesis. However, if I could figure out your argument, rest assured, I'd prove you categorically mistaken.

      --
      Just callin' it like I see it.
    4. Re:Why... by h4rm0ny · · Score: 4, Interesting


      Not only that, but names can help you remember which server is for what purpose. My four computers at one employer were 'Sadism', 'Masochism', 'Bondage' and 'Discipline'. I got away with that for nearly half a year before my team leader noticed. Anyway, Bondage was for all my admin stuff, emails, etc. Discipline was my test rig. Masochism my build scripts, et al. Sadism actual development. I was stretching the definitions a fair bit for some of those, but it did make sense to me. And was no suprise at all to those who knew me. ;)

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    5. Re:Why... by Ihmhi · · Score: 4, Funny

      Although it may be healthy to project personalities onto things (I'm a little skeptical, though I could maybe be persuaded by somebody who doesn't go around making sweeping psychiatric diagnoses of people he's never met) that hardly justifies encoding those projections into names.

      My printer wastes my time, money, and annoys the hell out of me without ever really doing any work - so I named it after my ex-girlfriend.

    6. Re:Why... by dimeglio · · Score: 3, Funny

      Here at the (anonymous) clinic we give our servers the name of disorders and conditions.

      Guess which server had RAM problems?
      Emphysema suddenly shutdown one day when its fan locked-up and overheated.
      All MS servers have names of various cancers. Macabre yes, but it keeps them from spreading.

      Our IT staff sounds quite impressive to the MDs when they're chatting in the cafeteria.

      Psychoanalyze that!

      --
      Views expressed do not necessarily reflect those of the author.
  42. Medical Conditions by IAmCthulhu · · Score: 5, Funny

    I was a network admin for a small law office, and I named all their computers after medical conditions. I named the senior partner's computer 'IMPOTENCE' hoping that someday he'd come to me and tell me that he was having problems with impotence and that he couldn't get it to come up.

  43. Re:Gomco, Mogen, Plastibell. by Wonko+the+Sane · · Score: 3, Insightful

    reduced risk of infection

    Soap and water?

    reduced chance of losing the whole damned thing to cancer

    We could also cure breast cancer by performing preemptive mastectomies.

  44. I use names of past lovers... by raehl · · Score: 4, Funny

    First server was nobody, followed by righty, lefty, and fleshlight.

    Next up is fido.

    What? I just need an echomail gateway.

  45. Oh man ... by Greedo · · Score: 3, Funny

    You can name servers? And here I was memorizing IPs ...

    --
    Tuus crepidae innexilis sunt.
  46. Re:Gomco, Mogen, Plastibell. by PotatoSan · · Score: 5, Informative

    Actually, the "piles of medical evidince" have lead the American Association of Pediatrics and the American Medical Association not to recommend routine circumcision of newborns. Given the number and density of nerve endings in the foreskin, comparison to clitoridectomy is not so far-fetched. Just because the one is socially accepted where you live doesn't make it any less barbaric than the other.

  47. Re:Not religious freedom, but.... by Stormwatch · · Score: 4, Insightful

    I think if the sensations during intercourse with my wife were even more intense, my head would explode.

    Here's an analogy... it's like they altered your eyes to make you see in black and white; and someone says you could have a "more intense" vision. Not ever knowing color, you can only imagine that as increased brightness. And you think, no, I don't need more brightness.

    But it's not just more of what you know. It's something you don't know at all.

  48. Re:Gomco, Mogen, Plastibell. by khanyisa · · Score: 4, Insightful

    19 cross-sectional studies, 5 case-control studies, 3 cohort studies, and 1 partner study showed that the relative risk for HIV infection was 44% lower in circumcised men. Where's your evidence?

  49. Re:Gomco, Mogen, Plastibell. by Hognoxious · · Score: 4, Funny

    Chop the whole thing off and I'm sure you could get even more of a reduction.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."