On Fri, 19 Apr 2002, Luke Mewburn wrote:

> what about just having a section at the top of the rc.d script itself
> that sets the defaults?

>  --> new section follows
>  --> contains "defaults: " and then a description of what it does
> 	# defaults: set date and time via NTP
> 	ntpdate=NO
> 	ntpdate_flags="-b -s"

> this could be used by a script to build the default sushi form files
> as well...

I gather sushi would need just a little more information than that,
namely, the variable type and possible values. E.g.:

	# === default values and descriptions ===
	ip6mode=autohost	# description: IPV6 mode
				# possible: host,autohost,router
	# === end defaults ===

	# === default values and descriptions ===
	rcshutdown_timeout=""	# possible: any numeric value
	# === end defaults ===

Note, for multiple variables, you may want to associate a different
description with each. *_flags would not need it's own description.

It should be safe to assume that any variable set to "YES" or "NO"
would have possible values of only "YES" or "NO", and anything not
specified would admit an arbitrary string.

The second example isn't currently set in any script, but for the
purpose of generating sushi's form file, all such variables could
be set in a dummy script.

Frederick