At 03:14 a.m. 23/12/2005, you wrote:
>freenetwork at ... writes:
>-- snip --
>> The freenet node runs with the name "javaw.exe". But if you don't know the
>> exact PID, simply killing by name
>> might affect other java programs running as they all have the same process
name (java or javaw).
>> "
At 03:14 a.m. 23/12/2005, you wrote:
>[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
>-- snip --
>> The freenet node runs with the name "javaw.exe". But if you don't know the
>> exact PID, simply killing by name
>> might affect other java programs running as they all have the same process
name (ja
freenetwork at ... writes:
-- snip --
> The freenet node runs with the name "javaw.exe". But if you don't know the
exact PID, simply killing by name
> might affect other java programs running as they all have the same process
name (java or javaw).
> "freenet.exe" is just the bunnyapp
Yeah, but
>>> Right now this isn't directly possible via freenet.exe (the systray app) as
>>> far
>>> as I can tell. It does take command line args, but not a shutdown one. It
>>> could
>>Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown to call
>>ExitFServe would spawn a new process t
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
-- snip --
> The freenet node runs with the name "javaw.exe". But if you don't know the
exact PID, simply killing by name
> might affect other java programs running as they all have the same process
name (java or javaw).
> "freenet.exe" is just the bun
>>> Right now this isn't directly possible via freenet.exe (the systray app) as
>>> far
>>> as I can tell. It does take command line args, but not a shutdown one. It
>>> could
>>Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown to call
>>ExitFServe would spawn a new process t
At 12:24 p.m. 20/12/2005, you wrote:
>Bob writes:
>> Right now this isn't directly possible via freenet.exe (the systray app) as
>> far
>> as I can tell. It does take command line args, but not a shutdown one. It
>> could
>Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown t
At 12:24 p.m. 20/12/2005, you wrote:
>Bob <[EMAIL PROTECTED]> writes:
>> Right now this isn't directly possible via freenet.exe (the systray app) as
>> far
>> as I can tell. It does take command line args, but not a shutdown one. It
>> could
>Heh ignore that, I'm an idiot, obviously running free
Bob writes:
> Right now this isn't directly possible via freenet.exe (the systray app) as
> far
> as I can tell. It does take command line args, but not a shutdown one. It
> could
Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown to call
ExitFServe would spawn a new proces
Anonymous writes:
>
> I believe with *nix and BSD, it is possible to stop Freeent with the shell
script. Is there any way to shut down
> or stop Freenet with the Windows client with the command line? This would be
useful for the task scheduler
> and such!
>
> Thanks
Right now this isn't direct
Bob <[EMAIL PROTECTED]> writes:
> Right now this isn't directly possible via freenet.exe (the systray app) as
> far
> as I can tell. It does take command line args, but not a shutdown one. It
> could
Heh ignore that, I'm an idiot, obviously running freenet.exe -shutdown to call
ExitFServe would
Anonymous <[EMAIL PROTECTED]> writes:
>
> I believe with *nix and BSD, it is possible to stop Freeent with the shell
script. Is there any way to shut down
> or stop Freenet with the Windows client with the command line? This would be
useful for the task scheduler
> and such!
>
> Thanks
Right n
12 matches
Mail list logo
