Otherwise, though, it leaves directories alone. Permissions for the new dir, so it just copies the permissions from the Installfiles does make kind of an educated guess - if it has to createĪ directory because it doesn't exist on the target, it has to pick some To slack, however, they are all just directories. In your case, for instance, you care about /opt/httpd, but not /opt. Slack has no idea what level of the parent directories you care about. You have to create all the parent directories in the tree, but Meta-data config file (like rpm or bundle would, or like your tableĪbove). Putting them in a tree, rather than also having to describe them in some > If so, would you take an RFE to improve fixfiles to also sync directoryīasically, the problem is that slack lets you install files by just > It looks like for now we'll have to forget about fixfiles and just set > stdin and apparently that list doesn't contain the directories > but /usr/lib/slack/slack-installfiles takes a list of files to sync on > /var/lib/slack/stage/roles/svn/files/opt/httpd/conf
> Our fixfiles does set all the perms right, as seen in > opt/httpd/conf/ssl.key root svn-team 2550 > opt/httpd/conf/ssl.crt svn svn-team 2775 > change directory perms in the hopes that slack-installfiles would them. > in the hope of finding some details on whether fixfiles is allowed to TODO: clean up this email into a more general doc.
0 kommentar(er)
