[freenet-dev] ready to dump after 22h... but

> On Mon, Nov 18, 2002 at 09:03:44AM +0100, Anonymous wrote: > > ok, but what I need to do under win2k? On win2k the easiest way of getting the thread stack traces is to start freenet in a console process. To do this, open a command prompt and type cd "c:\program files\freenet 0.5" java -cp freen

RE: [freenet-dev] ready to dump after 22h... but

> On Mon, Nov 18, 2002 at 09:03:44AM +0100, Anonymous wrote: > > ok, but what I need to do under win2k? On win2k the easiest way of getting the thread stack traces is to start freenet in a console process. To do this, open a command prompt and type cd "c:\program files\freenet 0.5" java -cp freen

[freenet-dev] ready to dump after 22h... but

On Mon, Nov 18, 2002 at 09:03:44AM +0100, Anonymous wrote: > Oskar wrote: > > killall -s SIGQUIT java > > Don't do "killall" in unix... > > ok, but what I need to do under win2k? Suffer? I know I did. > My node is on a win32 system. > (killall is for *nix) > > anyway I'm stalled with, growing,

[freenet-dev] ready to dump after 22h... but

Oskar wrote: > killall -s SIGQUIT java > Don't do "killall" in unix... ok, but what I need to do under win2k? My node is on a win32 system. (killall is for *nix) anyway I'm stalled with, growing, 314threads (max=300) bye ___ devl mailing list devl at

Re: [freenet-dev] ready to dump after 22h... but

On Mon, Nov 18, 2002 at 09:03:44AM +0100, Anonymous wrote: > Oskar wrote: > > killall -s SIGQUIT java > > Don't do "killall" in unix... > > ok, but what I need to do under win2k? Suffer? I know I did. > My node is on a win32 system. > (killall is for *nix) > > anyway I'm stalled with, growing,

[freenet-dev] ready to dump after 22h... but

Oskar wrote: > killall -s SIGQUIT java > Don't do "killall" in unix... ok, but what I need to do under win2k? My node is on a win32 system. (killall is for *nix) anyway I'm stalled with, growing, 314threads (max=300) bye ___ devl mailing list [EMAIL