1 |
On 08/03/12 16:55, Frank Steinmetzger wrote: |
2 |
> On Thu, Mar 08, 2012 at 12:50:40PM +0200, Nikos Chantziaras wrote: |
3 |
>> On 08/03/12 04:57, Frank Steinmetzger wrote: |
4 |
>>> It came to my attention that during (after) an emerge run, df reports |
5 |
>>> considerably less space available on my / than before the emerge |
6 |
>> |
7 |
>> That's because the old files are not being deleted since they are in |
8 |
>> use. When you logout of KDE and restart the whole stack |
9 |
>> (/etc/init.d/xdm restart) then everything will be back to normal. |
10 |
> |
11 |
> By jove, that's definitely it. I knew about this fact from other use cases |
12 |
> (like deleting a video file which I'm still watching. HA, do that, Windows!), |
13 |
> but never thought of it regarding emerging. I always assumed for some reason |
14 |
> that the files were kept in RAM and the physical file itself was no longer |
15 |
> relevant. Just closing all programs before logging out gave back around 350 M. |
16 |
|
17 |
I discovered this nifty little tool recently that tells you if any |
18 |
deleted files are currently being kept open by running processes: |
19 |
"app-admin/checkrestart". I usually run it after world updates so I can |
20 |
tell whether I need a restart or not. |