Jordan Brown writes: > This isn't the first time there's been a service that needs to run > during shutdown, after other things have been shut down. SunUC's > automatic mechanisms for installing "single user" patches have roughly > the same requirement, give or take exactly where during shutdown. (I > have never looked at that sequence in detail, but I have seen that it > runs too early in shutdown.)
That's likely a different case with a different set of issues. For instance, SunUC would probably be unhappy if /usr and /var were unmounted before it ran. > However, I suspect that for this particular operation (cutting power to > the UPS) a kernel hook _is_ required. I assume that when you cut power > to the UPS, pretty much instantly the computer loses power. That means > it better happen after the final sync, which is down inside the kernel > inside uadmin(2). (Perhaps others realized this, but I don't see it > clearly in the messages.) Unfortunately, you also have to talk *to* the UPS to get there. It's not all that simple to do as a kernel service. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
