Re: mulitlog not getting terminated when Red Hat reboots?

> - What is 'outage', in the context of mulitlog?

It means that multilog died without a SIGTERM.  In your case, what's  
probably happening is that multilog is exiting cleanly due to the  
SIGTERM from shutdown, but then it's getting restarted by supervise  
(which either hasn't gotten SIGTERM yet or has been restarted by  
svscan which hasn't gotten SIGTERM yet).

> - How can I arrange for mulitlog to think there _isn't_ an outage
>   when we reboot?

You have to first kill svscan, then do 'svc -d /service/*', then  
(after a moment for the log services to flush any last messages) do  
'svc -d /service/*/log'.  If you don't care about any last messages  
from your services, you can kill svscan, then do 'svc -d /service/* / 
service/*/log'.  You can use the 'killall' script to kill svscan, or  
find some other way (such as running it under supervise...).

You can put the commands in a script in /etc/init.d and put an  
appropriately-named symlink in /etc/rc0.d and /etc/rc6.d.  (Or is it / 
etc/rc.d/rc0.d and /etc/rc.d/rc6.d?)