Ticket #627 (closed defect: fixed)
Permissions Entries have no effect for ConfigFiles
| Reported by: | Martin <[email protected]…> | Owned by: | desai |
|---|---|---|---|
| Priority: | minor | Milestone: | POSIX unification |
| Component: | bcfg2-client | Version: | |
| Keywords: | Cc: |
Description
I noticed that when I use the Permissions tag of the Rules generator to specify filepermissions of configuration files that have also been specifed by the ConfigFile? tag, the values of the Permissons Tag have no effect:
When the bcfg2 client runs it first changes the permission to the specified value. Just after that it changes it again to the default value 0644 or whatever is set in the info or info.xml file.
Is this behavior intended or is it a bug?
Attachments
Change History
comment:1 Changed 14 years ago by solj
- Milestone changed from Bcfg2 0.9.6 Release to Bcfg2 1.0 Release
comment:2 Changed 14 years ago by solj
- Milestone changed from Bcfg2 1.0 Release to POSIX unification
comment:3 Changed 14 years ago by solj
- Status changed from new to closed
- Resolution set to fixed
This behavior is intended. ConfigFile? permissions are set via :info/info/info.xml files. Permissions entries are intended to 'not care' about file contents, only permissions. With the changes in trunk, you should now be forced into using only one or the other (via Path entries). If both are specified, you will receive an error stating that the path is served using multiple generators.
comment:4 Changed 2 years ago by James colleen <[email protected]…>
Interesting - I would have thought that this was a bug. When I specified via Path entries I did get the error saying that the path was served using multiple generators.
https://techmechanic.blogspot.com/2021/02/windows-or-mac.html
