search for: bolthol

I see that there are an assorted bunch of "provider" types for resource type user. Are there not any "local file" providers for it? I have need of ensuring that certain local user accounts get created on all machines, reguardless of what the system "/bin/password" and "useradd" type mechanisms are set to. It would be really nice to find a pre-written

We have an existing "management system" of sorts, based on rdist. I''d like to know the best way to migrate it to using puppet. Currently, we have a local binaries tree, rdisted out nightly. We also make use of rdist''s extra capability to trigger scripts when and if named files are updated. I''m not sure what the best method would be, of converting this to

Hello folks, I''ve been looking into how I might check (and possibly set) svc properties via puppet. The closest I''ve found, is the provider/service/smf stuff. However, that seems to only allow enabling and disabling of services. NOT of configuring properties. Is there some way I dont know of, how to do that? If not, and I need to write something... under which module/plugin/

...nd a nifty tool called 'pkg-get'. My sysadmin (who has an HP-UX and Debian bias) thought this was the best he had seen, ahead of apt-get and yum, for example. This box already had everything I needed to build R, including gcc3, gcc4, libreadline and libiconv. pkg-get is at http://www.bolthole.com/solaris/pkg-get.html if it was not already installed. As far as I can tell, OpenSolaris aka Solaris Express Community Edition aka 'Solaris 11' can be built to have the same set of tools. (We will probably do so on an older box in due course.) I've written up what we needed to...

I recently built openssh 2.1.1p1, under solaris. I noticed that I had problems running scp. It seems that it could not find the executable on the remote end. This was odd, becuase it existed in /usr/local/bin, publically executable, and /usr/local/bin/was in the users' normal PATH (exported, even). So finally, I twiddled the source to make it call /usr/local/bin/scp, instead of just

We have an odd situation with a puppet 3 installation. It isnt serving out the module local files. We understand (Somewhat) about the new auth.conf requirements, and have filled those out. So, access to things such as puppet:///files/etc/somefile.conf are working fine. However, attempts to access puppet:///modulename/somefile.conf fail, with (in the case of modulename==java) Error:

PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

I''ve been looking around for instructions on installing puppetmaster with a standalone passenger, without apache. I''m a personal believer in, "the fewer layers, the better" :) Unfortunately, I cant find any instructions for this configuration. Everything seems to be written for "puppet AND httpd and passenger". Could anyone point me to instructions sans

Hi folks, I''ve poked around the language reference, and havent found anything on this so far. I''d like to be able to force a clean early exit from a module. WITHOUT encasing the whole body of the module in an if statement. What I''m looking for: class somemodule { #no this isnt going to be a global variable I''m just using that as an example, if

Howdy coders, in openssh-2.5.2p2, auth1.c, do_authentication() you folks do a call to getpwnam(user) If this fails, you NULL out 'pw' Unfortunately, this stops start_pam() from being called at all. I'm not a PAM API expert, but I was under the impression that there are pam API calls you should be making for account verification, in PARALLEL to getpwnam(), rather than being

Thanks go to Darren Tucker who posted about "#if 0" on auth-pam.c I saw his email in the archive, about solaris 7. I removed the "#if 0", and finally, password expiration works. A caviat or two: If UseLogin=no (the default) , if a user fails to use the correct password for a "change on first login" account, you get the following message: sshd(SYSTEM): Sorry,

I'm seeing broken transfers when attempting large amounts of data. I have read the issues.html file about the transfer dying issues, which claims, " Sometimes fatal error messages from the remote machine can be lost on the way to the client; you should investigate on the server for something stopping the transmission. The most common cause is that the destination disk is full."

Please note: this is a "cross posting" of sorts, from a post I made; http://groups.google.com/group/comp.unix.solaris/browse_thread/thread/a8bd4aab3918b7a0/528dacb05c970748 It was suggested that I mention it here. so I am doing so. For convenience, here is mostly a duplicate of what I posted, with a couple of minor updates. Please note: I''m not asking for technical help on

https://projects.puppetlabs.com/issues/14368#change-101086 Summary: (We dont need to improve our public documentation, because people can go BUY documentation for puppet) I can understand changing it to low priority or something. But *Rejecting* this issue? For a supposedly "free, open source" project? Really? This does not motivate me to continue advocating for use of puppet, let