emerge -e world problem

[swingkyd]

So I was performing an:

Code: Select all

emerge -e world

on my home computer while at work by ssh'ing into my computer at home.
Now, I was using putty for this which usually has a habit of timing out when I'm not babysitting it with a superflerous keystroke every few minutes.
However, after the putty session timed out, I usually have to re-log-on and do an:

Code: Select all

emerge --resume

to get things going again...but NOT this time.
INstead, I could no-longer access my computer via ssh. I waited until I got home to find to my horror, that my computer had been brought to it's knees: ie. it had completely frozen and I had to hard-reboot.

Does anybody know what might have happened? It doesn't seem normal to me to have an ssh connection bring the computer to a frozen and unresponsive state.

Thanks!

[Dammital]

No idea what happened, but I suggest you use screen when you login from work and do those long emerges. That way you can start up something that's long-running and disconnect/reconnect at will.

[To]

The advice about screen it's the best anyone can give you about this. I also spent lots of time connect to my home computer from work. I learned to use screen cause my connection closes from time to time.

[swingkyd]

sweet! thanks! for anyone who is interested, there is a good howto here:
http://jmcpherson.org/screen.html
AT least it's a bit easier to read than the GNU one.
Cheers.