I was afraid that this would be the case.
I do not have access to the source code -- the sysadmins install
xemacs through some sort of rpm thingie, and all I get are the .elc
files in the end. Learning how to build the whole of xemacs from
scratch is way beyond my limit.
I therefore make a humble feature request: that somebody turn this
into a run-time option rather than a build-time option.
Thank you for your assistance,
lauri
Thus spaketh Stephen J. Turnbull on 11/18/2006 08:08 AM:
Laurelin of Middle Earth writes:
> My situation: I use gnuserv/gnuclient. My site's Security Gurus are
> complaining about the fact that gnuserv is listening for incoming
> connections on an open port,
And well they might!
> It looks to me as if what I *want* to do is to force the use of unix
> sockets rather than internet sockets. Is this something that I can do
> without somehow finding a different build of xemacs (or rolling my
> own)? Is it a configuration option, or must it be built in at compile
> time?
It's compile time. On or near line 54 of lib-src/gnuserv.h you will
find the line
#define INTERNET_DOMAIN_SOCKETS
Change it to
#undef INTERNET_DOMAIN_SOCKETS
and rebuild. This is very low-tech, I know, but nobody's ever
contributed a patch to make this a configurable option (either via
configure at build time or in Lisp at runtime).
In theory, you could just run ./configure and then "make gnuserv" in
the lib-src directory and save some time. However, I can't promise
that gnuserv doesn't depend on any of the configuration options chosen
by your vendor (Red Hat, I guess?)
> I hope I've explained this clearly enough.
Certainly, it was very clear.
HTH
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta