Re: Invoking isboothook
"Luke A. Kanies" <[email protected]>
| Newsgroups | gmane.comp.sysutils.isconf.devel |
|---|---|
| Message-ID | <Pine.GSO.4.51.0302121600070.25758@pixie> |
On Wed, 12 Feb 2003, Stephen Schaefer wrote: > How? I've got a jumpstart script installing rc2.d/S990isconfInstall, > which invokes isboothook with "install" (and which deletes itself on > success), and also rc2.d/S99isconf which invokes isboothook with "boot". > But I also see provision to invoke with "start": when do you use that? > Is it worth using for "cron"? I added the 'start' for people who didn't really know what they were doing; it sets the context to 'NULL', which means that nothing with a specified context gets run. It and 'BOOT' are the only special contexts. So, I usually just run 'isboothook start' when I need to run isconf manually, but 'isboothook boot' needs to be run at boot time, in case any new BOOT context items have to be run. I think that at this point 'install' doesn't really do anything; it's essentially a hook, left in case I need to do something but mainly a holdover from ISconf2. Luke -- "The Microsoft Exchange Information Store service depends on the Microsoft Exchange Directory service which failed to start because of the following error: The operation completed successfully." ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf