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 A6DD4138825 for ; Wed, 12 Nov 2014 05:58:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 62DF8E0992; Wed, 12 Nov 2014 05:58:41 +0000 (UTC) Received: from mail-qg0-f54.google.com (mail-qg0-f54.google.com [209.85.192.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 34371E092E for ; Wed, 12 Nov 2014 05:58:40 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id q108so8195921qgd.41 for ; Tue, 11 Nov 2014 21:58:39 -0800 (PST) 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=jidu6dkFhzCsOiAle9F4Pq6Hh+i1voMseK7xPdIQiBg=; b=SGx6kLrmD5WfbyFcPFMfbiKOhlMpN2TC6kaZugv+kRWSYzMsP2gYGNHwKXpBZQtg+X ZX6PylHBAl03eoPiF3nXKpo8ZUb+NE2wyQZKacSpNax+QZJ+M88fIH9zfmM7xv0WIXTz LD492q0psOTIiMGiD3ORZx4H7bZck/qhO6Ug0msWzrOH4TOY9ZGmKS3BZSRdVwHSHGNV 4r46e1d7H4WCAe2zQ2GtWqQjBmXfFM6LN4X0pMEsEj3luuWpm38EuLV6Aa7qVQlNE5DV p7oMhO/aVAPk73ctenTU5L57nWNODcqk6Ogmyny8aF8kijfUVbF4RcJpjldZozRvrXLq Dljg== X-Received: by 10.229.209.136 with SMTP id gg8mr52215038qcb.16.1415771919113; Tue, 11 Nov 2014 21:58:39 -0800 (PST) Received: from [192.168.2.5] (adsl-98-95-148-49.jan.bellsouth.net. [98.95.148.49]) by mx.google.com with ESMTPSA id 91sm13870943qgy.15.2014.11.11.21.58.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Nov 2014 21:58:38 -0800 (PST) Message-ID: <5462F70D.5090907@gmail.com> Date: Tue, 11 Nov 2014 23:58:37 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 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] Re: gcc 4.7.3 --> 4.8.3 References: <9194407.LW02KBNQ1l@wstn> <20141110222302.6adfe4ef@digimed.co.uk> <5461DC1A.80503@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 23ced8fe-7c06-470a-aad2-88458a4ed645 X-Archives-Hash: 3df9eff5dedca7db7b6972f84bdaa517 James wrote: > Dale gmail.com> writes: > >> After I do a major upgrade or --emptytree, I switch to boot runlevel, >> check with checkrestart and restart whatever it reports needs it.=20 >> Generally, switching to boot runlevel catches most everything. > OK, so I emerge checkrestart and ran it. And there are almost a dozen t= hings > it says need a reboot (mostly lxde). "These processes do not seem to ha= ve an > associated init script to restart them". > > So I have to reboot anyways. Oh, the url on the "checkrestart" script > now points to some advertisement that is unrelated, to a bug needs to > be file to the github location? I did not know if this is the best new > link, so I did not file this bug on checkrestart. > > > > ******************* >> Yea, rebooting may be faster but I hate rebooting all the time. :/ > Agreeded. But after a gcc update, I think it wise, especially since > gcc-4.9 cometh....soon? > >> Dale > thx, > James > > If checkrestart says there is no init scripts to restart the process, odds are you don't need to really worry about it. That said, I use htop to find out what is running and do what I can to restart them anyway.=20 Usually when I get that message, restarting udev or lvmetad gives me a clean output.=20 Usually if a gcc is released that requires all this, it is well known.=20 Any gotchas related to gcc will spread like fire. There is to many people using gcc for something of that nature to sneak by plus the coders usually know this and make it known as well. It's been a good while since the rebuilding of everything has been required. I tend to do it myself but I don't get my hands to dirty over the deal. I usually do it the next time there is a KDE upgrade or something since that rebuilds a lot of packages anyway.=20 Just something to ponder on. ;-) Dale :-) :-)=20