I apologize if this is a resend....


Late last night when my brain may have been working at only 3%, I upgraded
from ad12 to ad13, by downloading the source and building (on red hat linux).

Upon installation, I ran aolserver, using the sample-config.tcl file.  That
worked fine.

So I killed the server and restarted it using my development scripts.  My
development scripts use the technique where within the script, the name of
the server is obtained from AOLserver using [ns_info server]

set server [ns_info server]

and then generic sections within the config file are demarked such as

  ns_section /ns/server/${server}/module/nslog
  ns_param  extendedheaders  host

while server specific sections might be enumerated with

  ns_section /ns/server/theashergroup/module/nsopenssl
  ns_param  port  444

In short, within my config.tcl file I have about a dozen servers defined
and then to start aolserver, I have a script that starts a specific server
to start by passing the -s server flag to nsd8x

nsd8x -s theashergroup -tconfig.tcl -u nsadmin -g web

When I restarted the server none of this worked, and my 3am debugging seems
to reveal that the value of [ns_info server] is "" at the time the config
file is evaluated.

So, here's the question: do you see this behavior or does this appear to
work correctly for you?  How do you start your aolserver 3.3 ad13s?

Thank you,

Jerry Asher



=====================================================
Jerry Asher                       [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161    Tel: (510) 549-2980
Berkeley, CA 94709                Fax: (877) 311-8688

Reply via email to