You cannot use svccfg directly from your jumpstart to add the dependency because the system has not booted and the repository doesn't know about the services yet. You could use an rc script (that would copied onto the filesystem during the jumpstart) that would execute the appropriate svccfg commands but the dependency would not be valid for the first boot after the jumpstart (and this is not an elegant solution). Now, you could create your own "my-system-log" service (which manifest is similar to system-log.xml but contains all the necessary dependencies). The manifest would be copied to the target system during the jumpstart. Of course, you would have to modify your site.xml to disable "system-log" and enable "my-system-log" instead.
-- Renaud > So, I'm starting to get a pretty good feel for this whole SMF administration > game. I managed to get a site.xml setup which gets rolled in during my > jumpstart process. I've found however that the "system-log" service starts > before my "nfs-client" service has finished mounting all it's targets. This > leads to my syslog file locations not being available when syslogd starts up. > I went through the steps outlined in the SMF FAQ "part 2.2" and added the > dependency. Now I want to know is there a way to make my change portable so > that I can roll that into my jumpstart as well. > > Any help would be greatly appreciated. > Thanks in advance. > > > This message posted from opensolaris.org > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
