How do you deal with dependency cycles around things like the root user? I'm
ending up defining files with uid=0,gid=0 rather than root, root just to
avoid dependancy cycles.
--
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.
--
You received this
Hi,
What does the root user depend on that you're getting in to dependency
cycles over?
Cheers,
On Thu, 2012-06-14 at 12:24 -0700, Jo Rhett wrote:
How do you deal with dependency cycles around things like the root
user? I'm ending up defining files with uid=0,gid=0 rather than
root, root
It doesn't, but many things in stage Main depend on the root user. It appears
that a user can only exist and be depended on in a single stage, and that
hardly makes sense for users like root...
On Jun 14, 2012, at 12:28 PM, Stephen Gran wrote:
What does the root user depend on that you're
I organize the root user in the first stage (before apt-get update!) and then
everything else in a subsequent stage.
Later I found out that puppet will write files as root:root, 0644 in the
default configuration. That meant I could remove many owner, group, mode
attributes from my file
My quick take is that declaring this:
user { 'root': }
Means that suddenly every file resource which says this...
owner = root
...now implicitly depends on that user resource. So unless you use require =
User['root'] in your owner=root file resources, things will break as some
resources will
On Jun 14, 2012, at 12:33 PM, Christopher Wood wrote:
I organize the root user in the first stage (before apt-get update!) and then
everything else in a subsequent stage.
Yep, this turns out to be the answer. More cyclic problems here but I've worked
through those.
--
Jo Rhett
Net
