On 18-Dec-00 18:12:01, Matt Sealey said:
>Hello Kevin
Actually, I think there's a mixup here. I was the original poster.
>> Sometimes.... well, oftenish... when I try to quit Miami I'm told that
>> I can't because V's network and file server is still running.
>Even after you ask Miami to try and kill them? Both V and V's net
>process should exit when the IP stack tells them to..
Yes. If I ask Miami to try and kill them, it says it can't. This only
happens some of the time.
>> Right now, top shows V _and_ V's network and file server both running,
>> and consuming tiny amounts of CPU time, but possibly significant
>> amounts of memory - certainly I have less free memory than I ought to
>> have right now.
>Which version of V is this?
3.2.13
>> _sometimes_ v's network and file server consumes 100% of my cpu time,
>> which is more annoying.
>Under what circumstances?
I should have said "sometimes". I've not spotted a pattern at all yet.
It's much rarer than the "still running" problem.
--
Adam Atkinson ([EMAIL PROTECTED])
"Our royal family died out because the last queen was impregnable."
"No, she was unbearable." "No, she was inconceivable."
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
