Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 76907 invoked from network); 25 Feb 2006 04:28:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Feb 2006 04:28:14 -0000 Received: (qmail 52884 invoked by uid 500); 25 Feb 2006 04:28:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 52860 invoked by uid 500); 25 Feb 2006 04:28:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 52851 invoked by uid 99); 25 Feb 2006 04:28:13 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2006 20:28:11 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 994CDDD for ; Sat, 25 Feb 2006 05:27:50 +0100 (CET) Message-ID: <1033745855.1140841670625.JavaMail.jira@ajax.apache.org> Date: Sat, 25 Feb 2006 05:27:50 +0100 (CET) From: "Bryan Pendleton (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)' In-Reply-To: <815873769.1137053603540.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-809?page=comments#action_12367758 ] Bryan Pendleton commented on DERBY-809: --------------------------------------- Hi Kristian, I think maybe there is one more place that needs to be changed, around line 65 of NetworkServerControl.java, where it says:
  • logconnections {on | off} [-h <host>] [-p <portnumber>]: This turns logging of connections and disconnections on and off. Connections and disconnections are logged to derby.log. Default is off.
    • What do you think? Do we need to remove "and disconnections" from this section as well? thanks, bryan > Incorrect documentation for 'NetworkServerControl.logConnections(boolean)' > -------------------------------------------------------------------------- > > Key: DERBY-809 > URL: http://issues.apache.org/jira/browse/DERBY-809 > Project: Derby > Type: Bug > Components: Documentation, Javadoc > Versions: 10.0.2.1, 10.1.1.2, 10.1.2.1 > Reporter: Kristian Waagan > Priority: Minor > Fix For: 10.2.0.0, 10.1.3.0 > Attachments: DERBY-809-1a-javadoc.diff, DERBY-809-1a-javadoc.stat, derby809.diff, radminconfigdb2jdrdalogconnections.html, tadminlogfile.html > > The documentation for 'NetworkServerControl.logConnections(boolean)' states that Derby logs both connections and disconnections. As of 10.1.2.1 and (all) earlier releases, this is not true. The documentation should be corrected to avoid confusing users. > The thought of adding logging of disconnections has also been posted on derby-dev. > Byran Pendleton identified the following documentation with the incorrect description: > http://db.apache.org/derby/javadoc/publishedapi/org/apache/derby/drda/NetworkServerControl.html > http://db.apache.org/derby/docs/10.1/adminguide/radminconfigdb2jdrdalogconnections.html > http://db.apache.org/derby/docs/10.0/manuals/admin/hubprnt23.html > http://db.apache.org/derby/docs/10.1/adminguide/tadminlogfile.html > Should we fix this in 10.0? If yes, please update fix versions for this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira