From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] system uptime
Date: Sun, 30 Aug 2015 01:08:32 -0400 [thread overview]
Message-ID: <29113.1440911312@ccs.covici.com> (raw)
In-Reply-To: <55E2851B.20301@gmail.com>
Dale <rdalek1967@gmail.com> wrote:
> Philip Webb wrote:
> > How long do desktop users typically leave their systems between reboots ?
> > How long between power off/on's ?
> >
> > I've long been in the habit of switching everything off while I sleep,
> > then restarting after I've woken & got going again myself.
> > However recently, I've run into delays getting my router
> > (only 1 device attached) to shake hands successfully with my ISP's server,
> > which have been requiring several power off/on's before it works.
> > As a result, I've started rebooting only after my weekly system update
> > -- it means I get to use the new versions of everything --
> > & not powering off at all ; the monitor + Xscreensaver are off
> > whenever I'm away from the machine for >= 1 hr (approx).
> >
> > Are there any pro's/con's I sb aware of ?
> >
>
>
> root@fireball / # uprecords
> # Uptime | System
> Boot up
> ----------------------------+---------------------------------------------------
> 1 193 days, 09:28:37 | Linux 3.5.3-gentoo Sat Sep 22
> 07:50:38 2012
> 2 116 days, 16:24:24 | Linux 3.16.3-gentoo Mon Oct 13
> 20:27:52 2014
> 3 111 days, 00:34:49 | Linux 3.18.7-gentoo Tue Mar 31
> 18:57:19 2015
> 4 101 days, 18:34:17 | Linux 3.5.3-gentoo Wed Dec 31
> 18:00:00 1969
> 5 72 days, 12:03:16 | Linux 3.9.5-gentoo Sat Jul 13
> 19:11:24 2013
> 6 69 days, 00:44:23 | Linux 3.11.6-gentoo Mon Jan 6
> 03:33:34 2014
> 7 66 days, 11:00:52 | Linux 3.9.5-gentoo Thu Oct 31
> 15:54:27 2013
> 8 51 days, 23:49:06 | Linux 3.13.6-gentoo Sun Mar 23
> 15:53:30 2014
> 9 46 days, 01:07:54 | Linux 3.16.0-gentoo Thu Aug 28
> 15:48:57 2014
> 10 36 days, 11:40:14 | Linux 3.14.0-gentoo Mon May 19
> 16:05:48 2014
> ----------------------------+---------------------------------------------------
> -> 28 6 days, 20:58:28 | Linux 3.18.7-gentoo Sun Aug 23
> 02:14:26 2015
> ----------------------------+---------------------------------------------------
> 1up in 1 day , 01:40:30 | at Mon Aug 31
> 00:53:23 2015
> t10 in 29 days, 14:41:47 | at Mon Sep 28
> 13:54:40 2015
> no1 in 186 days, 12:30:10 | at Thu Mar 3
> 10:43:03 2016
> up 1179 days, 07:42:13 | since Wed Dec 31
> 18:00:00 1969
> down 15497 days, 20:30:4 | since Wed Dec 31
> 18:00:00 1969
> %up 7.071 | since Wed Dec 31
> 18:00:00 1969
> root@fireball / #
>
>
> The biggest reason I shutdown, power failure. I use checkrestart to see
> if/when I need to restart something after doing updates. If for example
> I update something in the @system area, then I just logout of the GUI,
> go to boot runlevel, run checkrestart again to see if that did it and
> then go back to default runlevel. Sometimes, I have to restart
> something by hand instead of rebooting but not to often. Generally just
> going to boot runlevel gets the job done.
>
> One thing about not rebooting a lot, you use cache a lot which can speed
> some things up a bit. I have 16GBs here and most of the time, it is
> almost all used. How much that helps, I dunno but if it didn't help,
> they wouldn't have it doing it. Another good side, run updates while
> you sleep.
>
> The only bad side, more wear on things like fans and some extra dust. I
> try to clean my rig at least twice a year or whenever I notice the temps
> a little higher than they should be. Oh, pulls power all the time which
> may not matter much depending on your electricity rates.
>
> Of course, fixing that connection issue may be a good idea too. ;-)
hmmm, if you go to boot run level what is the difference between that
and rebooting? After a major update there are so many things to restart
that I usually give up and reboot the system, is actually quicker.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2015-08-30 5: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 [this message]
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
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=29113.1440911312@ccs.covici.com \
--to=covici@ccs.covici.com \
--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