On Jan 10, 2008, at 3:48 PM, Matthew Toseland wrote:
On Friday 04 January 2008 23:34, [EMAIL PROTECTED] wrote:
Author: robert
Date: 2008-01-04 23:34:20 +0000 (Fri, 04 Jan 2008)
New Revision: 16898
Modified:
trunk/freenet/src/freenet/node/fcp/FCPServer.java
Log:
don't get network port if disabled, lazy port-binding
Does this break configuring such things while disabled? I.e. are the
configs
registered and functional even when the service is disabled?
It should not, although I know of no way to activate the FCP/Fproxy
while it is running except through Fproxy. The only exception being if
the port *would-have-been-available* for binding at launch time, but
is not available when activated. This interfered with the simulator,
as the second node created would try and bind to the port and fail.
Now, r16899 does break enabling-while-disabled, but I believe that I
corrected that in r16900.
--
Robert Hailey
_______________________________________________
Devl mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
