I don't see us ever enabling the default instance. Our project is to replace the standard syslog on all of our platforms (Solaris, IRIX, Linux) with syslog-ng as part of our centralized logging project. Thanks for the advice!
Justin -----Original Message----- From: David Bustos [mailto:david.bus...@sun.com] Sent: Monday, October 23, 2006 2:23 PM To: Justin Lloyd Cc: smf-discuss at opensolaris.org Subject: Re: [smf-discuss] Re: Replacing syslog with syslog-ng Quoth Justin Lloyd on Mon, Oct 23, 2006 at 12:01:09PM -0700: > Since the Enhanced Profiles project seems a way off from being > implemented in Solaris, is the best solution for now is what Liane > recommended? I've implemented her recommendations, ensuring that I did > fully define the system-log dependencies and dependents in my > instance, and it seems to work well. We'd just have to be careful with > patches and upgrades. It depends on whether you'll ever enable system-log:default . If not, then you can just leave it. Otherwise, you should - Make a copy of /var/svc/manifest/system/system-log.xml - Delete the create_default_instance line. - Copy in your <instance>...</instance> tag. This should leave system-log:default runnable. And I think if we ever change system-log.xml, it will update the service properties, but it won't change the properties on your instance. At that point you should recreate your manifest based on the new system-log.xml, and reimport. David
