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 07:08:07 -0400	[thread overview]
Message-ID: <CAGfcS_m-gd6q0QcuP3vf6okHoh8nXVshsNBGrgAxdXfJWFtirg@mail.gmail.com> (raw)
In-Reply-To: <55E2CFE6.7050303@gmail.com>

On Sun, Aug 30, 2015 at 5:41 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 30/08/2015 06:04, Philip Webb wrote:
>> How long do desktop users typically leave their systems between reboots ?
>> How long between power off/on's ?
>>
>
> Mine depends. I typically do a deliberate reboot only when wanting a new
> kernel running. Sometimes it's a few days, often up to a month or more.
>

++

Typically I reboot every week or two.  I try to keep up with stable
kernel releases on the latest longterm branch (currently 3.18.20).
I'm currently at 19 days, which is a bit on the high side for me, but
it seems like 3.18 hasn't had as many updates as some of the other
stable series.

If you keep a closer eye on security issues and care to track which
kernel fixes you do or don't accept, or want to mess with kernel live
patching, then you could go longer.  I also like to reboot at some
frequency just so that if for whatever reason it doesn't reboot I only
have a few week's worth of system updates to look at to figure out
what changed.  I have Gentoo hosts that I don't stay on top of as
often and when 5 things break at once I'm playing guessing games
(those hosts are all easy to snapshot).

-- 
Rich


  reply	other threads:[~2015-08-30 11:08 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 [this message]
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
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_m-gd6q0QcuP3vf6okHoh8nXVshsNBGrgAxdXfJWFtirg@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