search for: stoppard

I have been storing the output of facter in a database with the assumption that uniqueid was actually unique, until I found that it is the same for a handful of my machines. It appears that uniqueid is set from the output of hostid. I checked into hostid and it gets its value from gethostid(). The following link, http://www.opengroup.org/onlinepubs/009695399/functions/gethostid.html, states,

...penssh would call into openssl? The exact same code works fine on Linux, obviously. Any help would be greately appreciated. -c [Christopher Mason <cmason at cmu.edu> http://ash.rem.cmu.edu/ ] ["Don't you see?! We're actors--we're the opposite of people!" -Stoppard]

Hi everyone, I''m using a svn pre-commit hook to check manifests for syntax errors. I''ve recently upgraded puppet from 0.22.4 to 0.23.2 and the hook stopped working. I use the following command to parse .pp files: /usr/local/bin/puppet --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport /tmp/$$.pp Now, I make a decision based on the exit code. If 0 then commit, else exit

Greetings all, In beginning my quest into puppet. I came across a situation I would like for puppet to handle in a specific way, but I''m not sure if the ability currently exists. I''ve read about the various workarounds and limits on the ''file'' element, when using it to create directory structures (in regards to parent dirs). With that said, I was thinking

I''m running into a very odd occurrence. I started with a new puppet server and was able to add a few classes, however as I try and add new ones I get odd parsing error messages, the most common being Could not match ''}'' at whatever file. Here is the exact error I get err: Could not retrieve catalog: Could not parse for environment production: Could not match

I''ve been using puppet for a while but I just recently decided to start using it to manage crontabs. It works great but puppet is reporting (and being very noisy about it) every time it does a run even when there is nothing in the actual crontab to change. I think this is happening because I''m setting defaults for the Cron type, which I should be able to do. Right? eg: Cron {

Hello all, puppet hangs while trying to restart a daemon when the associated config file changes, here the log: Mar 19 11:30:04 ingentTest puppetd[27390]: Starting Puppet client version 0.22.0 puppetd[27390]: Starting configuration run puppetd[27390]: (/ingenttest/qualsevolnode/guaita[guaita]/File[/etc/guaita.conf]/content) synced puppetd[27390]: