[
https://issues.apache.org/jira/browse/DERBY-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3708:
-----------------------------------
Component/s: (was: Newcomer)
Derby Info: (was: [Patch Available])
Derby Categories: [Newcomer]
Unset patch available flag. The only attached patched has been committed.
Setting the fix version and resolving remains (if work is done).
I also unset "Newcomer" in the component list and ticked the new "Newcomer"
category box.
> setting tracedirectory from the command line does not work
> ----------------------------------------------------------
>
> Key: DERBY-3708
> URL: https://issues.apache.org/jira/browse/DERBY-3708
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: DERBY-3708_diff.txt
>
>
> I tried
> java org.apache.derby.drda.NetworkServerControl tracedirectory /tmp
> and got:
> Trace directory changed to /tmp.
> java org.apache.derby.drda.NetworkServerControl trace on
> Trace turned on for all sessions.
> Trace turned on for all sessions.
> And the trace output was not redirected to the /tmp directory. The
> tracedirectory command seemed to be ignored.
> Setting tracedirectory with the system property derby.drda.traceDirectory or
> with the NetworkServerControl api seems to work ok.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
