From: "Travis Bemann"
>The only comment is that *is this really the proper way to do this*?
>Should Freenet clients be able to restart the Freenet node at all,
>especially on multiuser systems and such (yes, UNIX is multiuser). In
>addition, if this is to get around some bug in Fred which forces
On Wed, Sep 26, 2001 at 10:33:06PM -0500, thelema wrote:
<>
> The Restart Node command should probably be an argument to the
> AdministrativeCommand command, so that you can send all sorts of
> authenticated administrative commands.
One might as well define different admin commands as different me
Hi,
I'd like to strongly request 2 easy new features for FCP.
15 minutes work for someone who knows the node code well.
1) Export ref
2) Restart Node
With these features, there won't be any need to run the jar file for any reason
except to start up the node.
Protocol details:
1) Export ref -
On Thu, Sep 27, 2001 at 05:33:55PM +1200, David McNab wrote:
> From: "Travis Bemann"
> >The only comment is that *is this really the proper way to do this*?
> >Should Freenet clients be able to restart the Freenet node at all,
> >especially on multiuser systems and such (yes, UNIX is multiuser).
On Thu, Sep 27, 2001 at 05:33:55PM +1200, David McNab wrote:
> From: "Travis Bemann" <[EMAIL PROTECTED]>
> >The only comment is that *is this really the proper way to do this*?
> >Should Freenet clients be able to restart the Freenet node at all,
> >especially on multiuser systems and such (yes, U
On Wed, Sep 26, 2001 at 10:33:06PM -0500, thelema wrote:
<>
> The Restart Node command should probably be an argument to the
> AdministrativeCommand command, so that you can send all sorts of
> authenticated administrative commands.
One might as well define different admin commands as different m
On Thu, Sep 27, 2001 at 01:23:56PM +1200, David McNab wrote:
> Hi,
>
> I'd like to strongly request 2 easy new features for FCP.
> 15 minutes work for someone who knows the node code well.
>
[snip]
> 2) Restart Node
>
> With these features, there won't be any need to run the jar file for any
>
On Thu, 27 Sep 2001, David McNab wrote:
> Hi,
>
> I'd like to strongly request 2 easy new features for FCP.
> 15 minutes work for someone who knows the node code well.
>
> 1) Export ref
> 2) Restart Node
>
> With these features, there won't be any need to run the jar file for any
> reason exce
On Thu, Sep 27, 2001 at 01:21:38AM -0400, Travis Bemann wrote:
> The only comment is that *is this really the proper way to do this*?
> Should Freenet clients be able to restart the Freenet node at all,
> especially on multiuser systems and such (yes, UNIX is multiuser).
We have already considered
From: "Travis Bemann" <[EMAIL PROTECTED]>
>The only comment is that *is this really the proper way to do this*?
>Should Freenet clients be able to restart the Freenet node at all,
>especially on multiuser systems and such (yes, UNIX is multiuser). In
>addition, if this is to get around some bug i
On Thu, Sep 27, 2001 at 01:21:38AM -0400, Travis Bemann wrote:
> The only comment is that *is this really the proper way to do this*?
> Should Freenet clients be able to restart the Freenet node at all,
> especially on multiuser systems and such (yes, UNIX is multiuser).
We have already considere
On Thu, Sep 27, 2001 at 01:23:56PM +1200, David McNab wrote:
> Hi,
>
> I'd like to strongly request 2 easy new features for FCP.
> 15 minutes work for someone who knows the node code well.
>
[snip]
> 2) Restart Node
>
> With these features, there won't be any need to run the jar file for any re
On Thu, 27 Sep 2001, David McNab wrote:
> Hi,
>
> I'd like to strongly request 2 easy new features for FCP.
> 15 minutes work for someone who knows the node code well.
>
> 1) Export ref
> 2) Restart Node
>
> With these features, there won't be any need to run the jar file for any reason
>exce
Hi,
I'd like to strongly request 2 easy new
features for FCP.
15 minutes work for someone who knows the node
code well.
1) Export ref
2) Restart Node
With these features, there won't be any need to run
the jar file for any reason except to start up the node.
Protocol details:
1) Exp
14 matches
Mail list logo