Quoth Justin Lloyd on Thu, Oct 05, 2006 at 08:27:56AM -0700: > At my company we are working on a centralized logging project, > standardizing on Syslog-NG across all platforms (Solaris 9 & 10, IRIX > and RH Linux). The problem I'm encountering is correctly defining > a syslog-ng SMF service (or instance of system-log?!) so that certain > dependencies continue to be met, such as rarp, without running into > the possibility of future upgrades and/or patches wiping out our > customizations. > > I've been tinkering with the NCsysng package at the Open-Systems > Group's blog > (http://opensystems.wordpress.com/2006/06/01/replacing-syslog-on-solaris-10-with-syslog-ng/), > but I still have not figured out the correct way to deal with the rarp > dependency. I initially thought that adding a dependent, but the > problem is that rarp has an explicit dependency on > svc:/system/system-log.
To be clear, you need rarp to depend on syslog-ng? In that case, you should be able to delete rarp's dependency on system-log, and put a dependent in your syslog-ng manifest. During upgrade, Solaris should consider the dependency deletion to be a customization, and not add it back. (In fact, you should be able to test this yourself, by modifying the dependency and reimporting the manifest.) David
