[Bug: 21.4.19] gnuserv-start

[Kevin Oberman]

> From: stephen at xemacs.org
> Date: Tue, 07 Nov 2006 15:39:10 +0900
> Sender: xemacs-beta-bounces 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.

For the record, adding an entry for the local host to the hosts file on
Andreas Bernauer's system fixed the problem and he can now use
gnuserv-start whether connected to the network or not.

Here is what I received from him:
    on xemacs-beta someone wrote that his gnuserv process exited right
    after startup.  I had the same problem.  You answered him:

    > You might try something like:
    > 127.0.0.1 myhostname localhost localhosts.my.domain

    This resolved my problem.  As I'm not subscribed to the xemacs-beta
    list, maybe you want to report that this resolved the issue or (at
    least) just take my thank you.

Maybe a small note somewhere in the gnuserv or gnuclient doc could
mention this potential problem.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
Url : http://calypso.tux.org/pipermail/xemacs-beta/attachments/20061127/0cc91436/attachment.pgp