Unable to specify duplicate sysctl value even though target is different

[kenmiller316]

Hi,

I'm working on a very LARGE project that wants node defaults and application updates to those defaults. vm.swappiness is a perfect example. By default they want 60, but certain applications need 0. I was hoping to manage both conditions with different sysctl.d/NN-target.conf files, but the second instance throws a duplicate declaration error.

Any chance this behavior could be changed?

Thanks,

== k+ ==

[trevor-vaughan]

@kenmiller316 As far as I know, you can only declare a given sysctl value once on a given system. You're going to want to abstract this one level up so that you can only manage it once per system.

Your best bet is probably to drive it via Hiera for your different types of nodes.

[raphink]

Technically, it would be possible to manage two values in different files with Puppet by setting up composite namevars on the type, but as @trevor-vaughan noted, it might not be the best approach in this case if sysctl doesn't support it.