| 1 |
On 2014-11-10 23:23, Neil Bothwick wrote: |
| 2 |
> On Mon, 10 Nov 2014 18:52:09 +0000 (UTC), James wrote: |
| 3 |
> |
| 4 |
>> > I'd have thought you needed to emerge -e world if you really want to |
| 5 |
>> > be protected. |
| 6 |
>> |
| 7 |
>> Yea, maybe. I read the man page on emptytree. I get it actually |
| 8 |
>> replaces |
| 9 |
>> by a "reinstall". Does this do more than if I just reboot after |
| 10 |
>> |
| 11 |
>> emerge @system @world and then reboot? |
| 12 |
>> |
| 13 |
>> I'd be curious to know exactly what reinstall does that is not |
| 14 |
>> covered by just starting up a given code again? |
| 15 |
>> |
| 16 |
>> Is it that it forces a reinstall and stop/starts the binary without |
| 17 |
>> rebooting? |
| 18 |
>> |
| 19 |
>> Rebooting catches *everything* even better than --emptytree ? |
| 20 |
> |
| 21 |
> --emptytree has nothing to do with rebooting. It simply forces emerge |
| 22 |
> to |
| 23 |
> rebuild everything in @world and their dependencies. Once you have done |
| 24 |
> that, you will have daemons still running the old code, which you could |
| 25 |
> fix with a reboot, or you could run checkrestart and restart only the |
| 26 |
> affected programs. |
| 27 |
> |
| 28 |
> After an emerge -e @world, a reboot is probably best, another reason to |
| 29 |
> avoid the unnecessary step of emerge -e @world in the first place. |
| 30 |
|
| 31 |
Or you can check the list of processes with deleted libraries and |
| 32 |
restart those. |
| 33 |
|
| 34 |
lsof -n | grep 'DEL.*lib' |
Archives