[Bug: 21.4.19] gnuserv-start

[stephen at xemacs.org]

Fran?ois Jouve writes:

 > * On more recent configurations (fedora 2, 4, 5) the situation is the
 > following:
 > 
 > - No network or cable network up (ethernet eth0) : gnuserv fails.

I actually don't recall anything like this since 2000.  Can you
provide URLs for the earlier discussions you found?

 > Other Features:
 >   Inhibiting IPv6 canonicalization at startup.

This is the only thing I can think of that seems related, but it
should not have anything to do with gnuserv.  It's something that
needs to be done by the main application (ie, the xemacs binary) to
conform to the IPv6 standard, but causes lots of problems in
practice.  That has been solved for 5 years, though.

There are two possible changes that might with your problem.  First,
it sounds to me like it's likely to be some kind of security
configuration problem.  Please check the gnuserv man page to see if
you can configure the GNU-SECURE protocol for your local host.  That
might help, without having to rebuild gnuserv.

Second, if you do not use gnuclient across the network, you could try
rebuilding gnuserv without the capability to use Internet domain
sockets.  That should remove all possibility of problems due to lack
of an internet connection.  AFAIK this requires configuring XEmacs
(your vendor may supply an appropriate config.h file), and then
editing the gnuserv.h file.

Change the line

#define INTERNET_DOMAIN_SOCKETS

to

#undef INTERNET_DOMAIN_SOCKETS

Whether these issues apply to your instance of gnuserv, I can't say,
because it looks like you're using vendor binaries.  Especially since
behavior changes across OS versions, you might get better help more
quickly by reporting the problem to Red Hat.

HTH.

Steve