[ 
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:

       <LI>logconnections {on | off} [-h &lt;host>] [-p &lt;portnumber>]:
        This turns logging of connections and disconnections on and off.
        Connections and disconnections are logged to derby.log.
        Default is off.</LI>

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

Reply via email to