[
https://issues.apache.org/jira/browse/QPID-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334855#comment-14334855
]
ASF subversion and git services commented on QPID-6247:
-------------------------------------------------------
Commit 1661931 from [~k-wall] in branch 'qpid/branches/0.32'
[ https://svn.apache.org/r1661931 ]
QPID-6247: Updates to configuration files should maintain existing file
permissions
Merged from trunk with commands:
svn merge -c 1661162 https://svn.apache.org/repos/asf/qpid/trunk
svn merge -c 1661530 https://svn.apache.org/repos/asf/qpid/trunk
> Updates to configuration files should maintain existing file permissions
> ------------------------------------------------------------------------
>
> Key: QPID-6247
> URL: https://issues.apache.org/jira/browse/QPID-6247
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.22, 0.24, 0.26, 0.28, 0.30
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Fix For: 0.32
>
>
> If I cause a change to made to the broker configuration (say, adding a port)
> or the configuration of a virtualhost backed by a json file (say adding a
> queue), the Broker rewrites the underlying file(JsonFileConfigStore).
> However, in doing so, the file's original file permissions may be lost. In a
> POSIX based system, get the default permissions specified by the umask.
> The user can workaround the issue by setting as suitably restrictive umask,
> but this will currently apply to all files created by Broker, even log files
> which a user may wish to carry a different permission, for operate reasons.
> The Java Broker should strive to maintain permissions on such file by
> attempting to replacement file with the same permission set/attribute view as
> the old.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
