Skip to content

I named my servers after exes and regretted it

General Discussion by prague1983 3 replies 154 views
6 #1

Just use descriptive hostnames. Skill issue. 🐧

But fine, since we are sharing: I once named a prod NFS server "STORAGE_OF_TEARS" after a breakup. Six months later I am screensharing with a client and they ask why their mount is slow and there it is in the df output, screaming at us both. Changed it to "nfs-01" that night. The ex found out anyway. Karma.

oops: 0000 [#1] SMP
#2
prague1983 said:
STORAGE_OF_TEARS
Pro tip: if you are stuck with bad names, Cloud Init can rename at first boot. Heads up, this breaks some Oracle Cloud metadata dependencies, so test first.

  • Set display name in console to something professional
  • Use hostnamectl in your startup script
  • Update /etc/hosts before any service binds to the old name

I have seen free tier instances with names like "temp-test-ignore" running production workloads for two years because nobody wanted to migrate. The shame compounds. Fix it early, fix it once.

licensing is a suggestion
#3

Check your provider TOS section on "acceptable naming conventions." Most hosts reserve right to rename or suspend for offensive strings. I think Contabo's terms have something about names that may embarrass the provider in support correspondence. You are not just risking your own reputation. Also, if client-facing, consider whether this constitutes professional negligence under your jurisdiction's duty of care standards. Definitions matter here.

8 #4

Named db cluster after beer brands. Client presentation. Cfo asked why query slow on "stella." whole room knew that bar. Never again. Ticket open with dignity. Waiting.

Vive la résistance... électrique

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft