search for: itsbruc

As far as I can tell, the "replace" parameter is all or nothing. What I am looking for is something like the exec/onlyif parameter that I can use to conditionally replace a file. Any thoughts ? “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this

Hi all, I am using Puppet to execute an Expect script (http://expect.sourceforge.net) on a client. The Puppet recipe, test.pp, is: exec { ''/root/test.exp'': command => ''/root/test.exp'', logoutput => true } The recipe runs correctly when run using ''puppet --debug --verbose test.pp'': debug: /Stage[main]//Exec[/root/test.exp]:

I have an odd situation where Samba 3.x domain members in an Active Directory 2008 R2 domain cannot authenticate the Administrator. All other users work, but if I try to connect to the samba services as the domain Administrator, authentication fails. The Windows domain controllers are happy to accept connections from the Administrator (e.g. using smbclient) but the Linux (Centos 5.5 and 5.6)

Does Puppet have any genuine concept of truth and nil that survives the interface with Ruby? has_variable? only returns false if a variable has never been assigned a value at all in the enclosing scope; there is no way to assign undef to a regular variable (as opposed to a resource parameter) within a scope and so make it undefined for the template. It would be a very useful thing to be able to

It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is this prohibition on "name" really the desired behaviour?

I've been testing DFS roots and I'm finding that while Vista and 2008 Server clients can connect with no problems, Windows XP Pro and 2003 Server clients fail. This seems like it's the wrong way round - Samba usually has more difficulties with recent Windows versions than older ones - but I can only assume that there's some registry/policy change between the versions. If anybody

Having set up two way trust between a Samba domain (with LDAP backend) and an AD domain, I find that 1. Users from the trusted domain are authenticated against the proper DC (that is, their regular password works), but only if there is a corresponding local domain user. 2. Users from the trusted domain are being mapped onto Samba/POSIX users associated with the local Samba domain, despite