Jira (PUP-4073) Child directories don't follow parent directories

[Nate Wolfe (JIRA)]

Title: Message Title

Nate Wolfe created an issue   Puppet / PUP-4073 Child directories don't follow parent directories Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2015/03/03 11:24 AM Labels: AIO Priority: Normal Reporter: Nate Wolfe There are several directories that are rooted under a parent directory, such as the $rundir and $logdir being under $vardir. If you do not rely on the default location of $vardir and specify it explicitly, the children directories do not move with it. For example: $ puppet master --configprint vardir /Users/nwolfe/.puppet/var   $ puppet master --configprint rundir /Users/nwolfe/.puppet/var/run   $ puppet master --configprint rundir --vardir=/tmp /Users/nwolfe/.puppet/var/run I would expect the output to be: $ puppet master --configprint rundir --vardir=/tmp /tmp/run Note that this behavior might be different between root and non-root. This ticket is concerned with the non-root case, which is what is used by Puppet Server when loading the Puppet ruby code into JRuby. I believe that in the early days of AIO this behavior was supported, but the implementation introduced some sort of cyclical dependency between various classes/modules, specifically the run_mode.rb and defaults.rb if I remember correctly. Add Comment   This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.