Hello, all. 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. Is there a right way to do this? Thanks, Justin This message posted from opensolaris.org