Re: Setting daemon as last thing to startup with SMF

googlegroups@xxxxxxxxxxxxxxxxx wrote:

Darren Dunham wrote:
Hmm... is that a hard requirement? I mean, how does it deal with things
that are started by cron or inetd that are technically "after" the boot?

Actually it is kinda a hard requirement... The software monitors system
processes and stuff and generates alerts if the processes aren't
running. It doesn't make sense to start the monitor before we start the
dataserver for example. Since the monitor can monitor anything, it
needs to run at the very end to avoid unnecessary alerts.

But you can enumerate what it is monitoring, and verify that you have
dependencies on all of them. That's slightly easier than "must run at
the end" given the syntax available to you.

I was kinda hoping there was a catchall dependency that forces it at
the end. When other apps start using SMF (we are the first), I can try
to force as many of them as possible to be a dependent of
multi-user-server. This way I can start up after.

The problem is that multi-user-server doesn't appear to be really
designed to be a point that things use much. Instead, more of a
catch-all for legacy rc3 scripts. So I don't know how much I'd go try
to keep using it.

As a matter of fact, there's a rather lengthy thread in the opensolaris
forums about it. You might want to browse through it.
http://www.opensolaris.org/jive/thread.jspa?threadID=6739&tstart=0

I'd probably depend on multi-user-server, then add explicit dependencies
for all services that don't otherwise reference it.

--
Darren Dunham ddunham@xxxxxxxx
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
.