James wrote: > Dale <rdalek1967 <at> 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. >> Generally, switching to boot runlevel catches most everything. > OK, so I emerge checkrestart and ran it. And there are almost a dozen things > it says need a reboot (mostly lxde). "These processes do not seem to have 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. Usually when I get that message, restarting udev or lvmetad gives me a clean output. Usually if a gcc is released that requires all this, it is well known. 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. Just something to ponder on. ;-) Dale :-) :-)
