Dale <rdalek1967 <at> gmail.com> writes: > > Neil Bothwick wrote: > >> Rebooting catches *everything* even better than --emptytree ? > > --emptytree has nothing to do with rebooting. It simply forces emerge to > > rebuild everything in <at> world and their dependencies. Once you have > > done, you will have daemons still running the old code, which you could > > fix with a reboot, or you could run checkrestart and restart only the > > affected programs.
Ah, that is what I thought. > > After an emerge -e <at> world, a reboot is probably best, another > > reason to avoid the unnecessary step of emerge -e <at> world in the > > first place. This conflict what others have said. Curious. My take is that since I updated the major compiler, gcc, it warrants an --emptytree rebuild and reboot, just to be safe. It's a workstation, not a server, so it's time for a reboot, imho. > 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
