[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unable to submit PR

From: Hans-Albert Schneider
Subject: Re: Unable to submit PR
Date: Thu, 17 May 2001 11:13:47 +0200 (MET DST)

>>>>> "LN" == Lakshmi Narayanan <address@hidden> writes:

    LN> Hi, Recently I have installed Gnats 3.113 in Red Hat
    LN> Linux release 6.2.  And I face the following problems:

    LN>    1. Running gnatsd says '520 You are not in the host
    LN> access list' error.

gnatsd looks in a file named gnatsd.access to check which hosts
are allowed access.  As your gnats installation seems to be in
/usr/local/gnats/..., it must be somewhere below that directory
(my first guess is /usr/local/gnats/etc/gnatsd.access).  The
format is explained in the file.

If the message appears when starting gnatsd from the command
line, this probably means that localhost (IP is not
listed in that file.  Unless you explicitely use localhost as
your gnats server, you can ignore that message.  Explicitely
having localhost as the gnats server is, in general, not what you
want, as then no other host can access the gnatsd.

I am starting gnatsd with an entry like this in /etc/inetd.conf:

support    stream  tcp     nowait  gnats   
/usr/local/gnats/libexec/gnats/gnatsd gnatsd

Make sure that the first field (in this example: "support") is a
known port, i.e., /etc/services (or the corresponding NIS map)
should map it to a port number.  the fifth field ("gnats") is the
user id under which the gnatsd should be running.

Note that this is not under the protection of TCP wrapper or
something similar, as gnatsd has got its own access control
mechanism (namely the gnatsd.access file).

Your second problem has already been competently answered, I
think (at least, smrsh is what I would think of, too).


Hans-Albert Schneider           <address@hidden>
Siemens AG                      phone:  (+49) 89 636 45445
Corporate Technology            fax:    (+49) 89 636 42284
Munich, Germany
 -- To get my public PGP key, send me a mail with subject "send key" --

reply via email to

[Prev in Thread] Current Thread [Next in Thread]