On Tuesday 03 Apr 2012 20:57:08 Ximin Luo wrote: > On 03/04/12 19:57, Matthew Toseland wrote: > > Nextgens is convinced that many of the problems users have installing on > > Windows are due to firewalls blocking the localhost connection between the > > wrapper binary and the JVM running Freenet. The usual solution proposed is > > to split up freenet-ext.jar, which infinity0 has been working on. Can we do > > a quick fix though? Just introduce the new wrapper jar on the classpath in > > new installs, so that it overrides the wrapper classes in freenet-ext.jar? > > The main difficulty appears to be update.cmd - on Windows, it will clobber > > wrapper.conf in some circumstances, in which case it could revert it to a > > version without the new wrapper.jar and thus break it. > > > > See bug: https://bugs.freenetproject.org/view.php?id=4075 > > How does splitting up freenet-ext.jar help with "not creating a localhost > socket"? > > i.e. can you explain the solution in more detail.
Wrapper 3.4 allows you to use a named pipe instead, from a config option in wrapper.conf. This avoids firewall issues and so hopefully results in a more reliable setup on Windows.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
