On Thu, 20 Mar 2008, Nicolas Williams wrote: > 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?
Because some of us manage non-Solaris systems, and because we don't _maintain_ the package involved, and because we're don't manage one box. > 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. Hand-editing XML is a non-starter. Using a specific fancy editor is a non-starter. Manually modifying the configuration of a live machine in order to extract something I can distribute to the rest of the facility, is a non-starter. Got any other approaches in mind? > 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. I think this thread has gone far afield from your original proposal. I think we reached, or at least approached, a consensus on how to acheive what you proposed without making life worse for those of us who have existing sshd_config files. IMHO you should not let the digression prevent you from pursuing the original proposal. -- Jeff
