From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 122AF1384C0 for ; Sun, 30 Aug 2015 12:33:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C380A14294; Sun, 30 Aug 2015 12:33:16 +0000 (UTC) Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9FDD614217 for ; Sun, 30 Aug 2015 12:33:15 +0000 (UTC) Received: by ykey204 with SMTP id y204so23195127yke.3 for ; Sun, 30 Aug 2015 05:33:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+J87QcGNVhVVu8Xe/KRv3XIDurEUwflH5DPpi4BLcM0=; b=VZ7/LwXwgCBpXT7Mh2zWCddVM0tMoQMsrGSU9JO2wXS4XnluPaDh4Bgqwrq1iHNJgo qovprLQVf1tz+nLJwATizdu86Hg6fZzlUmIxP6tqefTSAkT3IRT1Cgkt2jPTa/GF6gYr /Kpi/VaMs2v4bTRDxODRI+mz3Vc8kbZNY6RWNHoW7+mFmjljns8K61CPhHaKdXp8as1l 9guytKBfPc2yKXeI78uflHmQpko4ucZhRLiuQrASfEAe2y24BEFoZKZXgScvru7SWPMg v9/jIwA4e0jr2pxdusxCXdnSJpq7RsUn0GitqpmNU1G6ulckAM906SmjesxWuv8hlAO8 uwkQ== X-Received: by 10.129.128.130 with SMTP id q124mr12470752ywf.119.1440937994799; Sun, 30 Aug 2015 05:33:14 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-115-33.jan.bellsouth.net. [65.0.115.33]) by smtp.gmail.com with ESMTPSA id m132sm11133281ywb.34.2015.08.30.05.33.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Aug 2015 05:33:13 -0700 (PDT) Message-ID: <55E2F808.304@gmail.com> Date: Sun, 30 Aug 2015 07:33:12 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] system uptime References: <20150830040443.GA1081@ca.inter.net> <29113.1440911312@ccs.covici.com> <55E2B6A8.5080203@gmail.com> <201508301321.07980.michaelkintzios@gmail.com> In-Reply-To: <201508301321.07980.michaelkintzios@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 8a77768d-8789-4876-b74a-e26663f91e0e X-Archives-Hash: 7a78feec89b7c240c0aa011a9a12f4b2 Mick wrote: > On Sunday 30 Aug 2015 08:54:16 Dale wrote: >> covici@ccs.covici.com wrote: >>> Dale wrote: >>> >>> >>> 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. >> Hmmmm, this quoting thing didn't work right again. >> >> For me, it is faster. Also, rebooting can uncover a problem that I >> might not know about. I've had a few times where I couldn't reboot for >> some unknown reason. Plus, all the common stuff remains in cache. Most >> of the time tho, just logging out of a GUI, KDE for me, is enough. >> Using checkrestart should tell me exactly what needs to be restarted and >> most of the time how. About the only thing I have to restart manually, >> udev. It's one thing that has a regular update that doesn't restart >> since it is already started before getting to the boot runlevel. >> >> To each his own tho. All of us has our own way of doing things of this >> nature and for varying reasons. Some shutdown because electricity is >> expensive. For some, that doesn't matter. Some do it to just reduce >> noise from the fans etc. One reason I leave mine on all the time is >> that I almost always have mine doing something. I have tons of TV shows >> and such on here. If I'm not doing something myself, I have it doing >> something. >> >> Dale >> >> :-) :-) > What do you do if you install a new kernel? You have to reboot then, yes? > Of course. Don't you? I just don't have a huge need to update the kernel that often. I'm not running some server that has to worry about getting hacked 10,000 times a day. I just update it when I can. I might add, I'm stuck on the current kernel because NONE of the newer ones will boot. There's another thread on that where someone else has the issue. So, until that is fixed and I CAN update, no need worrying about a new kernel needing to be loaded. That just leaves me with power failures and such. Dale :-) :-)