Hey! I'm not sure if this is a problem with portage, or wget, but here's what happened. From work, I SSH to my home machine (both running Gentoo kept very current). The version of portage used is 2.0.45-r3. Here's what happend: 1) I had an emerge session going in a konsole to my home machine, and a few konsoles open on the local machine. After I was done with the konsole windows for the local machine, I went to close them. I accidentally closed the remote connection window instead. /me slaped his forehead. I didn't think anything much of it because I wanted to recompile the kernel on the local machine which I would need to reboot for anyway, so I let it go. 25 - 30 mins later (the local machine is kinda slow...), I rebooted and all was fine. I re-logged back into my home machine only to find the connection BRUTALLY slow. I've only got a 56k line at home (thus I DL packages during teh day from work, etc...). Anyway, once I was finally able to log back in to the home machine, I took a look at my connections to try and figure out why it could be as slow as it was (natsat -t). I found it was still connected to ibiblio. OK... so I looked at my processes and found wget still running. Once I killed wget, everything was back to normal and I re-emerged the packages I was DL'ing, everything was fine - it picked up where it left off. SO, long story short, either the unecpecited death of the emerge session (my closing the window) didn't tell wget it was dead, or wget didn't listen. I honestly don't know which it was. I mention the time it took to rebuild the kernel and reboot so you had an idea that this wasn't just a 30 second delay or something like that. It was almost a full half-hour. I just thought I'd let you know this. Also, this is re-producable. I tried it twice after I realized all this (even with the reboots to the local machine. Same thing everytime.
to be honest i really dont see this needs *fixing* ... wget would have closed once it finished d/lin said file
Might be better in recent versions. That's an odd circumstance. This wil probably be rememdied for later threading enhancements.
db fix
