Hi, You can find a "working" daemon here: http://github.com/ohadlevy/puppet/tree/puppetlisten under the ext/puppetlisten subdir.
It doesn't use inetd as ruby socket implementation does not work inet, I'm considering rewriting it in c but no real reason / time for now... search the mailing list for previous usage instruction (but its kinda straight forward..) Ohad On Tue, Apr 21, 2009 at 7:35 PM, Stasheck <stanislaw.kamin...@gmail.com>wrote: > > Ohad, I remember you were saiyng something about running puppet from > inetd - can you share some info? I really think that cron+inetd > combination would suit my company better than puppetd (which is > restarted every hour via cron) > > /br > Stanislaw > > On Apr 21, 10:03 am, Ohad Levy <ohadl...@gmail.com> wrote: > > We are using puppetd though cron, and it seems to me much more reliable > and > > much less resource hungry.. > > > > if you have more than a few clients, switch to mongrel/passenger. > > WAN is not a real issue if its stable, of course it takes longer runs > but... > > > > cheers, > > Ohad > > > > On Tue, Apr 21, 2009 at 3:19 PM, Jean-Baptiste Quenot <cara...@gmail.com > >wrote: > > > > > > > > > 2009/4/6 Mike Renfro <ren...@tntech.edu>: > > > > > > I'd normally expect that to work, but I just have puppet keep cron > > > > running, and have a periodic cron job that checks if puppet has died, > > > > and if so, restarts it: > > > > > Interesting, but why would you expect Puppet to die? Would you expect > > > Apache, Nginx or worse MySQL to die randomly like this? > > > > > I'm a Puppet user since nearly two years now, and in the big picture > > > of my web servers I find that puppetd is not the most reliable piece > > > of software. It dies every day, and my colleagues complain about this > > > regularly because their installed packages are not uptodate as they > > > expect. So I have to start it again and again on all machines. Is > > > Puppetd dying because of network problems? I believe so, but I think > > > it should be fixed instead of finding creative ways to keep puppetd > > > running, especially since I request it to run every 5 minutes as a > > > daemon. > > > > > Is anyone using puppetd in a WAN setup with default Webrick server > > > successfully? Shall I switch the HTTP server to Mongrel to gain > > > reliability? I'll test this setup. But if puppetd fails on the > > > client side, I'm not certain that changing the server's HTTP server > > > would actually prevent the client to fail at all... > > > > > I'm a bit eager with this, and I'm really looking forward to find a > > > solution, community-wise. Your comments are welcome. > > > -- > > > Jean-Baptiste Quenot > > >http://jbq.caraldi.com/ > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
