Jeff Trawick wrote: > > BTW, how would I query SUNWCapch22m to see what is there now?
AFAIK these clusters are just paperwork during SFW integrations (package RTI), they're not used nor do they map to anything on an installed system. Some of the nooks and crannies of historical SFW baggage. > If the user must make a modification to the config snippet (e.g., > wsgi.conf or sed.conf) in order to have the module perform any useful > work, shouldn't we put the config snippet in the samples-conf.d > directory instead of the conf.d directory? +1, if the conf cannot deliver anything sensible because it inherently needs user configuration (like sed), it is best to deliver into samples-conf.d Only conf files which are delivered by optional packages (or otherwise can do no harm) and deliver useful "Just Works Out of Box" functionality should drop into conf.d (example is SUNWapch22r-php52) -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
