There might be a bug, but again, you're on an EOL version of puppet. It's
entirely possible that any issue you're observing has been fixed already.
On Thu, Jun 22, 2017 at 11:56 AM Robert Inder
wrote:
> On 22 June 2017 at 14:42, jcbollinger
On 22 June 2017 at 14:42, jcbollinger wrote:
>
>
> On Thursday, June 22, 2017 at 5:26:41 AM UTC-5, Robert Inder wrote:
>
> I don't understand why the behavior you describe occurs, but I also don't
> understand why you are trying to set the owner of the link in the
> On 22 Jun 2017, at 15:42, jcbollinger wrote:
>
>
> So why not go with that? The link owner is relevant only to modifying or
> removing the link itself, and since you're managing it via Puppet, I don't
> see what purpose it serves to relax the permissions for
On Thursday, June 22, 2017 at 5:26:41 AM UTC-5, Robert Inder wrote:
I don't understand why the behavior you describe occurs, but I also don't
understand why you are trying to set the owner of the link in the first
place, especially if the directory containing it belongs to root.
>If I
On Wednesday, 21 June 2017 19:17:09 UTC+1, Rob Nelson wrote:
>
> Have you tried to create the link manually to see what happens?
>
By design, the directory containing the link is owned by root,
because we don't want anybody but root to be able create the link.
And root can use
ln -s -
Have you tried to create the link manually to see what happens?
Also you probably know but Puppet 3 is EOL. If the issue is with puppet
itself, rather than perms, it's going to require an upgrade to fix.
Unlikely, but wanted to make sure you're aware.
On Wed, Jun 21, 2017 at 1:13 PM Robert Inder
I'm hoping someone can help me diagnose a problem with
Puppet version 3.8.7 running on CentOS 6.4.
I have a couple of servers with a total of 43 web-accessed software
systems, each with its own unix user.
These installations are all created from scratch by Puppet, and then
the appropriate