seth vidal wrote: > 1. puppetd sucks..... memory. Indeed it does. This seems to be worse on the older ruby that is shipped in RHEL-5 than in Fedora, but it's still a non-trivial amount of ram. A lot of folks run puppet from cron for this reason. > I'd like to suggest we move to a cron-driven model instead of > puppetd. I'd write a simple cron job that runs every half hour to > run puppetd, if a lock file is not found. Pretty straightforward, of > course. You can probably avoid mucking with lockfiles yourself and just call puppetd. It will use /var/lib/puppet/state/puppetdlock by default. This is the same file that puppetd --disable writes. So if puppet is disabled or already running, you'll just get the message that puppet is skipping this run. (I'm preparing puppet-2.6.6 for fedora and epel -testing repos now, coincidentally.) -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You cannot propel yourself forward by patting yourself on the back.
Attachment:
pgp29TdJCwgmZ.pgp
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
