You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (Commented) (JIRA)" <ji...@apache.org> on 2012/04/02 17:43:23 UTC
[jira] [Commented] (DERBY-5442) Create documentation for
restrictive file permissions feature
[ https://issues.apache.org/jira/browse/DERBY-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244267#comment-13244267 ]
Dag H. Wanvik commented on DERBY-5442:
--------------------------------------
I believe your understanding is correct, Kim, with the added proviso to your paragraph two that the server must be started from the command line for the (new) default behavior to apply. You do mention that in your paragraph four. If the server is started via the API, the default is as before, i.e. as if the the property had been set to true. It is correct that a restarted engine does not "remember" the property's setting from the previous boot, so that is in deed a way to fall back. In the case of server started from the command line, the old behavior can only be secured by setting the property to false.
> Create documentation for restrictive file permissions feature
> -------------------------------------------------------------
>
> Key: DERBY-5442
> URL: https://issues.apache.org/jira/browse/DERBY-5442
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Fix For: 10.9.0.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira