Yeah, but whats the point of using SMF if you're just going to "set it and forget it?"
The power of SMF is that you want it to restart things when they have abnormal exit statuses. If you plan on using a transient SMF status that doesn't monitor the health of the process, then you might as well just use an /etc/init.d script on system startup. The only other advantage that SMF would give you over /etc/init.d on startup is service dependencies. I kind of wished SMF had a mode that wasn't "all or nothing" on this. It'd help me with my Splunk installation as well. =) If you do find out how to make SMF play nicely with child process having non-zero exit statuses, yet can still keep the primary process online, let me know. I'm a fan of SMF. On 12/2/10 9:48 AM, "no-re...@cfengine.com" <no-re...@cfengine.com> wrote: > Forum: Cfengine Help > Subject: Re: Cfengine Help: cf-execd: is daemon or cron better? > Author: berntjernberg > Link to topic: https://cfengine.com/forum/read.php?3,19555,19585#msg-19585 > > Hi, > > Maybe you can configure the smf manifest to be of type "transient mode" which > is like "run and forget". > This will start it at boot and leave it to your promises to restart it. > > Like this: > > > > > > > > > > Regards > /Bernt > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
