I would run puppet from a script (or cron) and just do something like: mount -o remount,rw / puppetd -o /etc/puppet/puppet.conf -o ..... mount -o remount,ro /
another small point, in my embedded playground, ruby/puppet needs at least 32mb system to run, if you want to run it as a daemon you need more memory/swap. (so another reason for a script vs service). cheers, Ohad On Thu, Jan 29, 2009 at 6:02 PM, Alex Kavanagh <tinwood....@googlemail.com>wrote: > > Hi > > I'm evaluating puppet to manage 77 embedded computers around the UK. > They will be installed in various electronic poster displays and > kiosks. > > In order to make the system more robust I intend to have the root file > system mounted read-only. > > I'm assuming that puppet needs to have write access to the file system > in order to make any changes. Thus, I would intend to remount the > filesystem to read-write prior to puppet making any changes and then > remount it back to read-only afterwards. > > Are there any obvious, or key, points in the puppet code where this > remounting can be done? Is it likely to be a big job? > > Many thanks for any help. > Cheers > Alex. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
