On Mon, Feb 17, 2003 at 05:31:46PM -0000, Dave Hooper wrote: > > > So, as originally stated, how to find the *actual* mainport.Port used > > > by fred in such a case? And in general terms how to achieve this for > > > any %'d conf value. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > You do not need to. Just default to 8888 and if the config file > > overrides it, then use that. And provide a way for the user to override > > it. > > ... And in general terms?! > How. Can. An. External. App. Find. Out. What. Fred. Uses. As. A. Default. > Value? Please? Imagine the user's config file hasn't been updated for some > time, and contains the line %defaultHTL=25 . Suppose a GUI configurator > wants to show the user what the default is. It can obviously not rely on > the value encoded by %defaultHTL for the reasons you've already stated: it's > a default that the devs are free to change in subsequent releases of fred > and the % indicates it's merely a comment that can be ignored. > > So once again I refer to my previous mails - the only way I can think of is > to create a dummy freenet.defaults by running configure with the --silent > option, and parse that. Is there any other way, yes, or no?
No. And there can never be, unless you assume a port for FCP, and we provide some of this functionality via FCP. And it is always possible, but unlikely, that we may have to change the FCP port. > > dave -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at ICTHUS.
msg06872/pgp00000.pgp
Description: PGP signature
