I have a little 16x2 lcd panel sitting in the front of my little gateway/mailserver. I wanted to display the basic boot/shutdown messages on it, then run my uptime/link status on it after boot. After looking around, I ended up adding a little bit to ebegin in functions.sh, dumping messages matching certain patterns to the serial device, and run my uptime/link script from /etc/conf.d/local.start

This works fine for what I want, but it did get me thinking.. Having a short summary for this ebegin info would be rather handy. As far as I have seen, the service startup/stop messages don't get logged (change vc or start X and they are gone) and maybe a simple pluggable way for setting off a generic or customized trigger when a service fails to start/stop?

The messages sent to ebegin tend to be long and awkward when trying to parse, and even worse damnit, these long message lines don't all fit on my 16 character wide panel. ;-)

Making the startup script changes I need on my gentoo boxen has been relatively straightforward for me, but still, it kind of feels like a dirty hack to me. I'll admit, it's the unix way, but I'd love some kind of clean way to add little extensions to do with startup stuff.

Thats my rant for the day.. :)

/ Mark Watkins
--
[email protected] mailing list



Reply via email to