Date: Sun, 30 Apr 2006 19:16:21 -0400 From: Coleman Kane <cokane@cokane.org> To: Eric Anderson <anderson@centtech.com> Cc: hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC Message-ID: <20060430231621.GA551@pint.candc.home> In-Reply-To: <444CE475.30104@centtech.com> References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > Eric Anderson wrote: > > Actually, some other things got changed somewhere in the history, that > broke some things and assumptions I was making. This patch has them > fixed, and I've tested it with all the different options: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > > It's missing the defaults/rc.conf diffs, but you should already know those. > > > Eric > I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. This allows the use of: rc_fancy="YES" ---> Turns on fancy reporting (w/o color) rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs rc_fancy="YES" rc_fancy_colour="YES" ---> Same as above for you on the other side of the pond. rc_fancy_verbose="YES" --> Turn on more verbose activity messages. This will cause what appear to be "false positives", where an unused service is "OK" instead of "SKIP". You can also customize the colors, the widths of the message brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and the contents of the message (OK versus GOOD versus BUENO). Also, we have the following message combinations: OK ---> Universal good message SKIP,SKIPPED ---> Two methods for conveying the same idea? ERROR,FAILED ---> Ditto above, for failure cases Should we just have 3 different messages, rather than 5 messages in 3 categories? TODO: One thing I am trying to figure out is how to get the terminal to report its width, in columns (which is something that VT100+ supports). I just don't know how to do it from a script. TODO: Get better reporting from the rc.d/* scripts (and whatever other services we track). Right now, if verbose is on, many services respond with OK when they aren't initialized, and some respond with SKIP/SKIPPED/FAILED. E.g.: pcvt will show "SKIP", but geli2 will show "OK". Neither of these two are enabled for me though. You may get it from here: http://www.cokane.org/files/rc_fancy-cokane5.patch Further: I am very open to suggestions regarding the rc.d/* system and its reporting mechanisms. I am even thinking that it might be a good idea to offer an overhauled set of scripts that forces functionality into the following framework: rc job offers result code (from which the OK,SKIP,ERROR, etc... are picked) rc job offers short (< 20 char) status message. This could be printed in a nice fashion just after the "Running start XXX", "Running stop YYY", which we currently display. rc job (or rc itself) offers name of job (geli2, moused, etc...). Thus, the lines are nice, consistent, and fluid. The "short status message" above would most likely be truncated to 20 chars (or so.). Hopefully, some of this can then start to be put into an rc-reporter such that I could run a command that could give me a nice report of rc/init: moused FAILED "short message" Gentoo has a nice script named rc-status that does similar. Though I am not too fond of its output format (job name at left, status at right edge, hard to find out what failed in a multiline report). Try this latest version, and drop a line back with your thoughts, criticisms, etc.... -- Coleman Kane cokane@cokane.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060430231621.GA551>