[Puppet Users] Adding Lines to *Existing* Files?

2010-11-01 Thread nickt
What, if any, is the best way to programatically add lines to an existing file with puppet? What I'm going for precisely is adding lines to either /etc/passwd and /etc/shadow (on Solaris) or /etc/ security/access.conf (on Linux) at "run" time. Adding lines to wind up with files along these lines,

[Puppet Users] Re: Solaris 10 Client "Default Provider for User" Woes Again

2010-10-27 Thread nickt
--verbose --trace --debug --server cmsvl01.d1.peapod.com --no-daemonize On Oct 27, 7:55 am, nickt wrote: > Thanks, Felix!  I figured it out.  Turns out it was because when I > copied my shadow.so (from ruby-shadow lib build) I'd not changed > permissions on it to be world read/execute.

[Puppet Users] Re: Solaris 10 Client "Default Provider for User" Woes Again

2010-10-27 Thread nickt
to add lines to allow login for specific LDAP groups. The only answer I've found so far is to use a module like concat, but I've not gotten that to work right so far. On Oct 27, 7:46 am, Felix Frank wrote: > On 10/27/2010 02:36 PM, nickt wrote: > > > Hopefully I'm jus

[Puppet Users] Solaris 10 Client "Default Provider for User" Woes Again

2010-10-27 Thread nickt
Hopefully I'm just missing something simple, but I'm having trouble getting just the absolute bare-bones puppet set up on a new, clean Solaris 10 install. When I try to run: /opt/csw/bin/puppetd --verbose --no-daemonize --server puppet.mydomain.com I just get: err: Could not create resources fo

[Puppet Users] Re: Problems with Solaris 10 & adduser

2010-10-14 Thread nickt
from cron, not puppetd. > > * nickt [2010/10/14 13:03]: > > > Oh!  (Thanks for the links! :)  Okay, that would make sense then, it > > must be trying to do the useradd as puppet user rather than as root. > > Then, how do people typically deal with this sort of thing on >

[Puppet Users] Re: Problems with Solaris 10 & adduser

2010-10-14 Thread nickt
And for that matter, why does it work "right" on Linux? If I run the puppetd with sudo ( sudo puppetd --server myserver.dom.com --verbose -- no-daemonize ) it works fine on Linux (or at least an Ubuntu 10.10 box). On Oct 14, 3:03 pm, nickt wrote: > Oh!  (Thanks for the links! :

[Puppet Users] Re: Problems with Solaris 10 & adduser

2010-10-14 Thread nickt
, 2:50 pm, Darren Chamberlain wrote: > According > tohttp://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/head/us..., > an exit status of 1 means No permission.   > (Seehttp://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/oam... > for the source to useradd.) >

[Puppet Users] Re: Problems with Solaris 10 & adduser

2010-10-14 Thread nickt
n 0.01 seconds Thu Oct 14 14:27:01 -0500 2010 Puppet (notice): Finished catalog run in 0.05 seconds Thu Oct 14 14:27:04 -0500 2010 Puppet (notice): Caught INT; calling stop On Oct 14, 11:34 am, Jeff McCune wrote: > On Thursday, October 14, 2010, Nigel Kersten wrote: > > On Thu, Oct 1

[Puppet Users] Re: Problems with Solaris 10 & adduser

2010-10-14 Thread nickt
No problem if I do that "by hand", as root. Just gives me the normal message, "64 blocks", and creates the account and directory as indicated. On Oct 13, 2:04 pm, Bruce Richardson wrote: > On Tue, Oct 12, 2010 at 07:59:40AM -0700, nickt wrote: > > > err: /Stag

[Puppet Users] Problems with Solaris 10 & adduser

2010-10-13 Thread nickt
I maybe be something stupid (just starting to learn Puppet :), but I'm getting problems trying to create new users. I just have a really simple /etc/puppet/modules/user/virtual.pp that looks like this: class user::virtual { @user { "user1": ensure => "present", comment => "\"Full Name\