public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Erwin, Richard D" <richard.d.erwin@boeing.com>
To: <help-gnats@gnu.org>
Subject: FW: gnats junk - access
Date: Tue, 29 Jul 2003 21:57:00 -0000	[thread overview]
Message-ID: <6E6ACC930A9BAB47AB0BBD1ACC0F8B38016A9DD8@xch-nw-02.nw.nos.boeing.com> (raw)



>  -----Original Message-----
> From: 	Erwin, Richard D  
> Sent:	Monday, July 28, 2003 4:08 PM
> To:	Erwin, Richard D
> Subject:	gnats junk - access
> 
> Folks;
> 
> I have gnats 3.999/4.0-beta installed, but have a problem concerning access.
> 
> /usr/local/com/gnatsdb/test/gnats-adm ("test" being out test database) has gnatsd.user_access.  The users are set at view - I've tried them set at edit.  Passwords are presently in text format, as we upgraded from gnats 3.113.
> 
> /usr/local/etc/gnats has gnatsd.host_access has the given compute servers through which gnats can be accessed set to none.  If I set localview to none, I get a 422 error and can't log into gnatsweb.  If I set localview to edit, I get into the database, password or no password, valid userid or not a valid userid.
> 
> CHDB shows...
> 
> CHDB test
> 210-Now accessing GNATS database 'test'
> 210 User access level set to 'none'
> 
> How should I set gnatsd.user_access within a given database, and gnatsd_host.access within the general area (/usr/local/etc/gnats) or withina given database (in this case, /usr/local/etc/gnats/test)?  What am I doing wrong here?
> 
> All advice gratefully accepted,
> 
> Rich Erwin
> Boeing SSG - M&CT Support
> (425) 865-3414


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

                 reply	other threads:[~2003-07-29 21:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E6ACC930A9BAB47AB0BBD1ACC0F8B38016A9DD8@xch-nw-02.nw.nos.boeing.com \
    --to=richard.d.erwin@boeing.com \
    --cc=help-gnats@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).