public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com> To: nobody@sourceware.cygnus.com Cc: gnats-prs@sourceware.cygnus.com Subject: Re: gnats/181: CHDB command must be issued twice in order to work Date: Sun, 26 Aug 2001 14:54:00 -0000 [thread overview] Message-ID: <20010826215400.22329.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR gnats/181; it has been noted by GNATS. From: Yngve Svendsen <yngve.svendsen@clustra.com> To: Milan Zamazal <pdm@zamazal.org> Cc: gnats-gnats@sourceware.cygnus.com Subject: Re: gnats/181: CHDB command must be issued twice in order to work Date: Sun, 26 Aug 2001 23:45:37 +0200 I've been debugging a little bit more. Something sometimes seems to be breaking down in the parsing of client commands. First, I try to CHDB to "helpdesk" by using the three-argument version of CHDB (chdb databasename username password): 200 hurre.clustra.com GNATS server 4.0-alpha ready. chdb helpdesk yngves xxxxxx 210-Now accessing GNATS database 'yngves' 210 User access level set to 'edit' gnatsd actually tries to change database to the supplied username. There is no database named "yngves", so this should not be possible at all. But this is not the whole story. On the theory that gnatsd uses the wrong argument (the second instead of the first one) when changing database, I tried the following: 200 hurre.clustra.com GNATS server 4.0-alpha ready. chdb helpdesk helpdesk helpdesk 210-Now accessing GNATS database '' 210 User access level set to 'edit' Thus, I still have no good theory to give you. - Yngve
next reply other threads:[~2001-08-26 14:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-26 14:54 Yngve Svendsen [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-09-04 11:43 pdm 2001-08-26 14:24 Yngve Svendsen 2001-05-27 8:54 Milan Zamazal 2001-04-23 7:24 Yngve Svendsen 2001-04-23 7:04 yngve.svendsen
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=20010826215400.22329.qmail@sourceware.cygnus.com \ --to=yngve.svendsen@clustra.com \ --cc=gnats-prs@sourceware.cygnus.com \ --cc=nobody@sourceware.cygnus.com \ /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: linkBe 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).