>>>>> "BR" == Brock Rozen <brozen@webdreams.com> writes:
BR> Thus having config-test use the config file is very important, since it
BR> would also have to test permissions based on the directories specified
BR> in the config file.
Ah, yes, I forgot about that.
BR> How WOULD I try it though if I have the config files in a seperate
BR> directory than the executables? It changes the whole scenario and
BR> config-test should be able to handle that.
Good point. Enclosed is the minimal patch which allows this (perhaps not
for inclusion, but at least for proof-of-concept). You can call
config-test like
wrapper config-test /path/to/bizarre.cf
and it will use it in place of the one that wrapper provides in the
environment. Someone really needs to write a comprehensive document
detailing how to do virtual domains, and that person isn't me since I have
<zip> experience in that area.
- J<
--- config-test.orig Wed Nov 27 16:41:00 1996
+++ config-test Wed Nov 27 16:41:59 1996
@@ -49,7 +49,7 @@
print "\n\tNon obvious things that cause headaches:\n\n";
&header('');
-$cf = $ENV{'MAJORDOMO_CF'};
+$cf = $ARGV[0] || $ENV{'MAJORDOMO_CF'};
if (require $cf) {
&good("\"require\"d $cf okay.");
Follow-Ups:
References:
|
|