public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system uptime
Date: Sun, 30 Aug 2015 12:03:30 -0400	[thread overview]
Message-ID: <CAGfcS_m9mrYh35v0OEredZvxh43sHEti5oX+gkQ9Frbx=zrhvg@mail.gmail.com> (raw)
In-Reply-To: <55E32748.6040603@gmail.com>

On Sun, Aug 30, 2015 at 11:54 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> Technically, we should do a power down test every 6 months or so, but
> that turns out not to be a yes/no test in real life; it's a yes/destroy
> test and no-one wants to make a decision either way. So we all sit in
> limbo and wait for some exterior event to decide for us (like black-outs)
>

Half the time these are ancient services that have long been replaced
but nobody can bring themselves to make the call to get rid of the old
servers.  Maybe there were 10M records in the database and 9.998M of
them were migrated to a new database, but due to some issue the rest
couldn't be, so the old server stays up just in case anybody ever
needs the old data, and so on.

Typically these would just stick around until finally some hardware
component fails, and then it gets written off.

Sadly, this course of forcing hands seems to be going away.  At work
somebody tried to hand me an ancient system to look after in my spare
time.  Apparently they just finished virtualizing it.  Go figure -
they have VAX VMs available for Linux these days.  The problem is that
KT and maintaining documentation and not being the person who gets the
finger pointed at when something goes wrong costs the company time and
money, and in this case for almost zero value.

Usually the problems with technology aren't technical in nature...

-- 
Rich


  reply	other threads:[~2015-08-30 16:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30  4:04 [gentoo-user] system uptime Philip Webb
2015-08-30  4:22 ` Dale
2015-08-30  5:08   ` covici
2015-08-30  7:54     ` Dale
2015-08-30 12:20       ` Mick
2015-08-30 12:33         ` Dale
2015-08-30  6:52 ` Walter Dnes
2015-08-30  9:41 ` Alan McKinnon
2015-08-30 11:08   ` Rich Freeman
2015-08-30 13:24 ` Michel Catudal
2015-08-30 15:24   ` Daniel Frey
2015-08-30 15:54     ` Alan McKinnon
2015-08-30 16:03       ` Rich Freeman [this message]
2015-08-30 13:26 ` Alan Mackenzie
2015-08-30 13:58   ` Rich Freeman
2015-08-30 14:21   ` Mick
2015-08-30 15:22   ` Volker Armin Hemmann
2015-08-30 13:54 ` Alec Ten Harmsel
2015-08-30 15:20 ` Volker Armin Hemmann
2015-08-30 15:56 ` Peter Humphrey
2015-08-30 16:01   ` Alan McKinnon
2015-08-30 17:00     ` Dale
2015-08-30 17:05       ` Alan McKinnon
2015-08-30 17:26         ` Mick
2015-08-30 17:50           ` Dale
2015-08-31  8:50           ` Peter Humphrey
2015-08-31  9:42             ` Alan McKinnon
2015-08-31 13:41               ` [OT] Was " Peter Humphrey
2015-08-31 14:39                 ` Alan McKinnon
2015-08-31 15:04                   ` [gentoo-user] Re: [OT] Was " James
2015-09-01 14:19                   ` [OT] Was re: [gentoo-user] " Peter Humphrey
2015-08-31 21:58                 ` Alan McKinnon
2015-08-30 16:06   ` Rich Freeman
2015-08-30 17:11   ` Michel Catudal
2015-08-30 17:56     ` Terry Z.
2015-09-03 15:32 ` Philip Webb
2015-09-03 17:25   ` Neil Bothwick
2015-09-03 18:12     ` Philip Webb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_m9mrYh35v0OEredZvxh43sHEti5oX+gkQ9Frbx=zrhvg@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox