> If m-u-s does not depend on our service, our service won't be started in > such a configuration. (Such a configuration is precisely the reason I'm > asking this question.) > > So I guess another way to look at it, a higher-level view, would be "if > the system is configured to boot to milestone/multi-user-server, should > random add-on services like management agents be started?".
I think Dave Miner remarked on an older thread that the single-user, multi-user and multi-user-server milestones were created because SMF designers decided to stick close to the old run levels. If one were to abandon the concept of run level and wholly embrace the concept of milestone, then what would make sense is none, all, and "maintenance", or maybe even "subset 1", "subset 2". And then it remains to be answered by the sysadmin what he wants running in milestone "maintenance", or milestone "subset 1", etc. Do you want service X to be part of m-u-s? Hard to say, without asking what sysadmin fuctions are typical when I boot into m-u-s. As to dependency on milestones, I think Liane and Dave Bustos have remarked that if you need a dependency on X, specify it directly, and don't specify a dependency on Y because you know that Y has a dependency on X. CT
