So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature ''libshadow'' debug: Failed to load library ''ldap'' for feature ''ldap'' debug: /Settings[/etc/puppet/puppetd.conf]/Settings[puppetd]/File[/var/puppet/state/state.yaml]: Autorequiring File[/var/puppet/state] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[puppetd]/File[/var/puppet/state/classes.txt]: Autorequiring File[/var/puppet/state] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs/#####################.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/puppet/run]: Autorequiring File[/var/puppet] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/csr_#####################.pem]: Autorequiring File[/etc/puppet/ssl] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/puppet/state]: Autorequiring File[/var/puppet] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/puppet/log]: Autorequiring File[/var/puppet] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/puppet/lib]: Autorequiring File[/var/puppet] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/private_keys/###################.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/puppet/ssl/public_keys/###################.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: Finishing transaction -606390474 with 0 changes -- --- Derek T. Yarnell --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Jul 13, 2009, at 2:13 PM, Derek Yarnell wrote:> So I have been trying to run puppet once in my kickstart %post > scripts but every time it detaches and daemonizes even though I have > explicitly stated otherwise. Am I missing something? > > # rpm -q puppet > puppet-0.24.8-1 > > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > debug: Creating default schedules > debug: Failed to load library ''shadow'' for feature ''libshadow'' > debug: Failed to load library ''ldap'' for feature ''ldap'' > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[puppetd]/File[/ > var/puppet/state/state.yaml]: Autorequiring File[/var/puppet/state] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[puppetd]/File[/ > var/puppet/state/classes.txt]: Autorequiring File[/var/puppet/state] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/certs/#####################.pem]: Autorequiring File[/etc/ > puppet/ssl/certs] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/etc/ > puppet/ssl]: Autorequiring File[/etc/puppet] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/ > puppet/run]: Autorequiring File[/var/puppet] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/csr_#####################.pem]: Autorequiring File[/etc/ > puppet/ssl] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/ > puppet/state]: Autorequiring File[/var/puppet] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/ > puppet/log]: Autorequiring File[/var/puppet] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[main]/File[/var/ > puppet/lib]: Autorequiring File[/var/puppet] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/private_keys/###################.pem]: Autorequiring > File[/etc/puppet/ssl/private_keys] > debug: /Settings[/etc/puppet/puppetd.conf]/Settings[ssl]/File[/etc/ > puppet/ssl/public_keys/###################.pem]: Autorequiring File[/ > etc/puppet/ssl/public_keys] > debug: Finishing transaction -606390474 with 0 changesIt''s not daemonizing there, it''s exiting -- if you use --onetime, it exits after the run. -- The Number 1 Sign You Have Nothing to Do at Work... The 4th Division of Paperclips has overrun the Pushpin Infantry and General White-Out has called for a new skirmish. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies <luke@madstop.com> wrote:> > It''s not daemonizing there, it''s exiting -- if you use --onetime, it > exits after the run. >It really does daemonize there, # ps axuww | grep puppet root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 0:00 grep puppet # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature ''libshadow'' debug: Failed to load library ''ldap'' for feature ''ldap'' ... debug: Finishing transaction -606656664 with 0 changes # ps axuww | grep puppet root 2518 88.0 6.0 19080 15412 ? Rs 17:41 0:00 /usr/bin/ruby /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 0:00 grep puppet It is doing --onetime correctly but still regardless of putting --no-daemonize or not it still forks into the background. -- --- Derek T. Yarnell --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Just for input, I haven''t been seeing this behavior with 0.24.8 (or any previous release) on Fedora. Trevor On Thu, Jul 23, 2009 at 17:43, Derek Yarnell<derektyarnell@gmail.com> wrote:> On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies <luke@madstop.com> wrote: >> >> It''s not daemonizing there, it''s exiting -- if you use --onetime, it >> exits after the run. > > It really does daemonize there, > # ps axuww | grep puppet > root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 0:00 grep puppet > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > debug: Creating default schedules > debug: Failed to load library ''shadow'' for feature ''libshadow'' > debug: Failed to load library ''ldap'' for feature ''ldap'' > ... > debug: Finishing transaction -606656664 with 0 changes > # ps axuww | grep puppet > root 2518 88.0 6.0 19080 15412 ? Rs 17:41 0:00 /usr/bin/ruby > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 0:00 grep puppet > It is doing --onetime correctly but still regardless of putting > --no-daemonize or not it still forks into the background. > -- > --- > Derek T. Yarnell > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Ok, this would seem to be a problem on RHEL4 w/ the built in ruby as my RHEL5 w/ the built in ruby works as I would expect running the same command. RHEL4 ships with, # ruby --version ruby 1.8.1 (2003-12-25) [i386-linux-gnu] What are other people doing on RHEL4 are you using the built in ruby or are you providing a newer version? Funny thing is that everything works just fine other than this with the built in ruby, I just wanted to make sure that in the %post install of the kickstart that puppet actually ran (if you background it the %post install will just finish and reboot before puppet has a chance to run). Anyone else been trying to do this? Thanks, derek On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan <peiriannydd@gmail.com>wrote:> > Just for input, I haven''t been seeing this behavior with 0.24.8 (or > any previous release) on Fedora. > > Trevor > > On Thu, Jul 23, 2009 at 17:43, Derek Yarnell<derektyarnell@gmail.com> > wrote: > > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies <luke@madstop.com> wrote: > >> > >> It''s not daemonizing there, it''s exiting -- if you use --onetime, it > >> exits after the run. > > > > It really does daemonize there, > > # ps axuww | grep puppet > > root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 0:00 grep > puppet > > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > debug: Creating default schedules > > debug: Failed to load library ''shadow'' for feature ''libshadow'' > > debug: Failed to load library ''ldap'' for feature ''ldap'' > > ... > > debug: Finishing transaction -606656664 with 0 changes > > # ps axuww | grep puppet > > root 2518 88.0 6.0 19080 15412 ? Rs 17:41 0:00 > /usr/bin/ruby > > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 0:00 grep > puppet > > It is doing --onetime correctly but still regardless of putting > > --no-daemonize or not it still forks into the background. > > -- > > --- > > Derek T. Yarnell > > > > > > > > > > >-- --- Derek T. Yarnell --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and installed puppet and got the same behavior on RHEL4. Can anyone confirm that --no-daemonize works for them on RHEL4? puppetd --onetime --no-daemonize --verbose --debug Thanks, derek On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell <derektyarnell@gmail.com>wrote:> Ok, this would seem to be a problem on RHEL4 w/ the built in ruby as my > RHEL5 w/ the built in ruby works as I would expect running the same command. > RHEL4 ships with, > > # ruby --version > ruby 1.8.1 (2003-12-25) [i386-linux-gnu] > > What are other people doing on RHEL4 are you using the built in ruby or are > you providing a newer version? Funny thing is that everything works just > fine other than this with the built in ruby, I just wanted to make sure that > in the %post install of the kickstart that puppet actually ran (if you > background it the %post install will just finish and reboot before puppet > has a chance to run). Anyone else been trying to do this? > > Thanks, > derek > > On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan <peiriannydd@gmail.com>wrote: > >> >> Just for input, I haven''t been seeing this behavior with 0.24.8 (or >> any previous release) on Fedora. >> >> Trevor >> >> On Thu, Jul 23, 2009 at 17:43, Derek Yarnell<derektyarnell@gmail.com> >> wrote: >> > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies <luke@madstop.com> wrote: >> >> >> >> It''s not daemonizing there, it''s exiting -- if you use --onetime, it >> >> exits after the run. >> > >> > It really does daemonize there, >> > # ps axuww | grep puppet >> > root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 0:00 grep >> puppet >> > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug >> > debug: Creating default schedules >> > debug: Failed to load library ''shadow'' for feature ''libshadow'' >> > debug: Failed to load library ''ldap'' for feature ''ldap'' >> > ... >> > debug: Finishing transaction -606656664 with 0 changes >> > # ps axuww | grep puppet >> > root 2518 88.0 6.0 19080 15412 ? Rs 17:41 0:00 >> /usr/bin/ruby >> > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug >> > root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 0:00 grep >> puppet >> > It is doing --onetime correctly but still regardless of putting >> > --no-daemonize or not it still forks into the background. >> > -- >> > --- >> > Derek T. Yarnell >> > >> > > >> > >> >> >> >> > > > -- > --- > Derek T. Yarnell >-- --- Derek T. Yarnell --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
I no longer have a RHEL4 system to try it on but our standard until a few months ago was RHEL4 and puppetd --test certainly used to work (--test includes --no-daemonize) I seem to remember that we had other problems with Ruby as supplied by Centos4 so we installed these: ruby-1.8.5-5.el4.centos.1.i386.rpm ruby-irb-1.8.5-5.el4.centos.1.i386.rpm ruby-libs-1.8.5-5.el4.centos.1.i386.rpm ruby-mode-1.8.5-5.el4.centos.1.i386.rpm ruby-rdoc-1.8.5-5.el4.centos.1.i386.rpm Didn''t see any problems after that. Derek Yarnell wrote:> I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and > installed puppet and got the same behavior on RHEL4. > > Can anyone confirm that --no-daemonize works for them on RHEL4? > > puppetd --onetime --no-daemonize --verbose --debug > > Thanks, > derek > > On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell > <derektyarnell@gmail.com <mailto:derektyarnell@gmail.com>> wrote: > > Ok, this would seem to be a problem on RHEL4 w/ the built in ruby > as my RHEL5 w/ the built in ruby works as I would expect running > the same command. > > RHEL4 ships with, > > # ruby --version > ruby 1.8.1 (2003-12-25) [i386-linux-gnu] > > What are other people doing on RHEL4 are you using the built in > ruby or are you providing a newer version? Funny thing is that > everything works just fine other than this with the built in ruby, > I just wanted to make sure that in the %post install of the > kickstart that puppet actually ran (if you background it the %post > install will just finish and reboot before puppet has a chance to > run). Anyone else been trying to do this? > > Thanks, > derek > > On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan > <peiriannydd@gmail.com <mailto:peiriannydd@gmail.com>> wrote: > > > Just for input, I haven''t been seeing this behavior with > 0.24.8 (or > any previous release) on Fedora. > > Trevor > > On Thu, Jul 23, 2009 at 17:43, Derek > Yarnell<derektyarnell@gmail.com > <mailto:derektyarnell@gmail.com>> wrote: > > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies > <luke@madstop.com <mailto:luke@madstop.com>> wrote: > >> > >> It''s not daemonizing there, it''s exiting -- if you use > --onetime, it > >> exits after the run. > > > > It really does daemonize there, > > # ps axuww | grep puppet > > root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 > 0:00 grep puppet > > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > debug: Creating default schedules > > debug: Failed to load library ''shadow'' for feature ''libshadow'' > > debug: Failed to load library ''ldap'' for feature ''ldap'' > > ... > > debug: Finishing transaction -606656664 with 0 changes > > # ps axuww | grep puppet > > root 2518 88.0 6.0 19080 15412 ? Rs 17:41 > 0:00 /usr/bin/ruby > > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 > 0:00 grep puppet > > It is doing --onetime correctly but still regardless of putting > > --no-daemonize or not it still forks into the background. > > -- > > --- > > Derek T. Yarnell > > > > > > > > > > > > > -- > --- > Derek T. Yarnell > > > > > -- > --- > Derek T. Yarnell > > >-- Trevor Hemsley Infrastructure Engineer ................................................. * C A L Y P S O * Brighton, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. * P * /*/ Please consider the environment before printing this e-mail /*/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
--test does do the right thing and doesn''t fork a copy into the background and does what I need it to do running the built in version of ruby (1.8.1) or running the new ruby (1.8.7). Anyway thanks again, derek On Fri, Jul 24, 2009 at 1:05 PM, Trevor Hemsley <trevor.hemsley@codefarm.com> wrote:> > I no longer have a RHEL4 system to try it on but our standard until a > few months ago was RHEL4 and puppetd --test certainly used to work > (--test includes --no-daemonize) > > I seem to remember that we had other problems with Ruby as supplied by > Centos4 so we installed these: > > ruby-1.8.5-5.el4.centos.1.i386.rpm > ruby-irb-1.8.5-5.el4.centos.1.i386.rpm > ruby-libs-1.8.5-5.el4.centos.1.i386.rpm > ruby-mode-1.8.5-5.el4.centos.1.i386.rpm > ruby-rdoc-1.8.5-5.el4.centos.1.i386.rpm > > Didn''t see any problems after that. > > Derek Yarnell wrote: > > I spoke too soon, I recompiled with ruby 1.8.7, added rubygems and > > installed puppet and got the same behavior on RHEL4. > > > > Can anyone confirm that --no-daemonize works for them on RHEL4? > > > > puppetd --onetime --no-daemonize --verbose --debug > > > > Thanks, > > derek > > > > On Thu, Jul 23, 2009 at 7:40 PM, Derek Yarnell > > <derektyarnell@gmail.com <mailto:derektyarnell@gmail.com>> wrote: > > > > Ok, this would seem to be a problem on RHEL4 w/ the built in ruby > > as my RHEL5 w/ the built in ruby works as I would expect running > > the same command. > > > > RHEL4 ships with, > > > > # ruby --version > > ruby 1.8.1 (2003-12-25) [i386-linux-gnu] > > > > What are other people doing on RHEL4 are you using the built in > > ruby or are you providing a newer version? Funny thing is that > > everything works just fine other than this with the built in ruby, > > I just wanted to make sure that in the %post install of the > > kickstart that puppet actually ran (if you background it the %post > > install will just finish and reboot before puppet has a chance to > > run). Anyone else been trying to do this? > > > > Thanks, > > derek > > > > On Thu, Jul 23, 2009 at 6:49 PM, Trevor Vaughan > > <peiriannydd@gmail.com <mailto:peiriannydd@gmail.com>> wrote: > > > > > > Just for input, I haven''t been seeing this behavior with > > 0.24.8 (or > > any previous release) on Fedora. > > > > Trevor > > > > On Thu, Jul 23, 2009 at 17:43, Derek > > Yarnell<derektyarnell@gmail.com > > <mailto:derektyarnell@gmail.com>> wrote: > > > On Tue, Jul 21, 2009 at 8:13 PM, Luke Kanies > > <luke@madstop.com <mailto:luke@madstop.com>> wrote: > > >> > > >> It''s not daemonizing there, it''s exiting -- if you use > > --onetime, it > > >> exits after the run. > > > > > > It really does daemonize there, > > > # ps axuww | grep puppet > > > root 2476 0.0 0.2 4036 644 pts/1 S+ 17:41 > > 0:00 grep puppet > > > # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > > debug: Creating default schedules > > > debug: Failed to load library ''shadow'' for feature ''libshadow'' > > > debug: Failed to load library ''ldap'' for feature ''ldap'' > > > ... > > > debug: Finishing transaction -606656664 with 0 changes > > > # ps axuww | grep puppet > > > root 2518 88.0 6.0 19080 15412 ? Rs 17:41 > > 0:00 /usr/bin/ruby > > > /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug > > > root 2541 0.0 0.2 4888 648 pts/1 S+ 17:41 > > 0:00 grep puppet > > > It is doing --onetime correctly but still regardless of putting > > > --no-daemonize or not it still forks into the background. > > > -- > > > --- > > > Derek T. Yarnell > > > > > > > > > > > > > > > > > > > > > > -- > > --- > > Derek T. Yarnell > > > > > > > > > > -- > > --- > > Derek T. Yarnell > > > > > > > -- > > Trevor Hemsley > Infrastructure Engineer > ................................................. > * C A L Y P S O > * Brighton, UK > > OFFICE +44 (0) 1273 666 350 > FAX +44 (0) 1273 666 351 > > ................................................. > www.calypso.com > > This electronic-mail might contain confidential information intended > only for the use by the entity named. If the reader of this message is > not the intended recipient, the reader is hereby notified that any > dissemination, distribution or copying is strictly prohibited. > > * P * /*/ Please consider the environment before printing this e-mail /*/ > > > > >-- --- Derek T. Yarnell --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---