Or, thinking a bit more, how about
ClientShutdownNode
EndMessage
This would take down the node, but keep it listening for FCP commands -
esp. ClientStartNode or ClientKillNode. All data would be flushed to disk.
Node only responds when shutdown processing completes.
ClientStartNode
EndMessage
Only valid after ClientShutdownNode - for restarts. Reads in all config
files and restarts from scratch. Replies to client when all startup
processing (eg stat()ing the store files) is complete.
ClientKillNode
EndMessage
Tell node to fall on its sword - destroy all processes etc. Sends a
reply saying node is dying. This reply doesn't guarantee that node is dead
yet.
This would need an additional field in freenet.ini (or .freenetrc):
NodeAdminAllowedHosts=127.0.0.1
----- Original Message -----
From: "David McNab" <[email protected]>
To: <devl at freenetproject.org>
Sent: Wednesday, June 06, 2001 09:55
Subject: Re: [freenet-devl] remote shutdown ???(was: Freenet Winstaller
test - June 3,2001 0240GMT)
> > There was once a proposition of introducing a hook as to tell the node
> > to shutdown itself. Isn't that possible now via FCP, XML, [add more
> > buzzwords here], or whatever? It would have to be possible from
> > localhost only or require some strict authentication. This would enable
> > some remote administration tasks as well (and introduce
> > vulnerabilities). So what do we think about this direction?
>
> Love it :)
>
> ClientTerminateNode
> EndMessage
>
> ----- Original Message -----
> From: "Sebastian Sp?th" <Sebastian at SSpaeth.de>
> To: <devl at freenetproject.org>
> Sent: Wednesday, June 06, 2001 02:56
> Subject: Re: [freenet-devl] remote shutdown ???(was: Freenet Winstaller
> test - June 3,2001 0240GMT)
>
>
> > Dave Hooper schrieb:
> > >
> > > > Tray popup: Stop and Restart Node: failed
> > > > Jun 3, 2001 2:33:09 PM:Normal:Couldn't load DataStore from
> > > > .freenet\store_23523
> > >
> > > I know why this is happening (it's actually a stupid race condition).
> > > However it is only now occuring because I was asked to
> > > 1. Use javaw.exe in preference to java.exe
> > > 2. Use Freenet.node.Node in preference to Freenet.node.gui.GUINode
> >
> > 1. I know that Java.exe does not properly shut down the node. That is
> > the reason why I had introduced the ugly "TerminateProcess" (?) call to
> > force the shutdown.
> >
> > 2. It saves about 3MB of RAM usage. I think that is worth it.
> >
> > > The issue is that there is no portable way to 'stop' a freenet node,
> that
> > > works with all combinations of java.exe, javaw.exe, Freenet.node.Node
> and
> > > Freenet.node.GUINode.
> >
> > There was once a proposition of introducing a hook as to tell the node
> > to shutdown itself. Isn't that possible now via FCP, XML, [add more
> > buzzwords here], or whatever? It would have to be possible from
> > localhost only or require some strict authentication. This would enable
> > some remote administration tasks as well (and introduce
> > vulnerabilities). So what do we think about this direction?
> >
> > Sebastian
> >
> > _______________________________________________
> > Devl mailing list
> > Devl at freenetproject.org
> > http://lists.freenetproject.org/mailman/listinfo/devl
> >
>
>
> _______________________________________________
> Devl mailing list
> Devl at freenetproject.org
> http://lists.freenetproject.org/mailman/listinfo/devl
>
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
