On Thu, Mar 20, 2008 at 03:19:55PM -0400, Kyle McDonald wrote: > Which is great for new things being developed *in* solaris. > > I was discussing this from the view point of an admin building or > installing some outside software package that doesn't have a solaris SMF > manifest already created for his/fer use. > > There's a decision to make there. It's not always cut and dry.
How is it not? I've written a manifest for rsync, and it was real easy and it added real value. I've even created services entirely via svccfg -- that's even easier than editing XML (admittedly, not terribly fun unless you have good XML tools at hand, or at least VIM), and you can still get XML back for backup and distribution purposes, by exporting the service you've created through svccfg. So there's multiple ways to do this (a la Perl!) -- pick the one you like best. This thread has gone on long enough. I think we (or at least I) can let SMF detractors have the last word. I'm not interested in another multi- hundred e-mail thread where nothing much happens. In this thread I proposed something, then withdrew it; it wasn't worth the trouble (I don't work on SunSSH for a living), even though I believe the proposal was fine. Nico --
