Re: [AOLSERVER] config file

2009-06-26 Thread Cesareo Garci’a Rodicio 

Hi

I think config file is:

/opt/aolserver/servers/openacs/etc/config.tcl

As Dave said before (-t file_config as argument to nsd command)

In this config file (i.e config.tcl) you can seek "pageroot" parameter 
so in the example:


http://www.aolserver.com/docs/admin/sample-config.tcl.txt

you can see:

set pageroot   ${homedir}/servers/${servername}/pages

So www file might be in "pages" directory of $servername (whatever it'd be)

Regards
Cesáreo



jon jon escribió:

When I do that command I get starting to read config file
Notice: nsd.tcl: using threadsafe tcl:
Notice: nsd.tcl: finished reading conig file.?
1631 ?  Sl   0:28 /opt/aolserver/bin/nsd -it 
/opt/aolserver/servers/openacs/etc/config.tcl -u pre-book -g prebook -b
 
sorry I didn't post all of the output. The reason I was looking for this 
file is to see what directory is serving out the webpages. I have never 
used aolserver before, I am used to apache web server. isn't the 
config.tcl just  a example config file for aolserver?

thanks

On Fri, Jun 26, 2009 at 10:47 AM, Rusty Brooks > wrote:


Config files are all per-webserver so there may be more than one.
Typically they're supplied on the command line using the -t option
and you can sometimes get them with ps...

ps ax | grep nsd
 3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
 9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks

The regular name is nsd.tcl but they can be called whatever you want.

If ps doesn't give up teh command line, find out how they're getting
started and look for the -t option in there.

jon jon wrote:

Hi,
I am searching for the aolserver conifg file. I did not build
this server so aolserver is not installed in
usr/local/aolserver. The only thing I know is that I think
aolserver is installed in the opt directory. But  I don't know
what the config file is usually named for aolserver. The server
I am using is running fedora, so any help to find a name of a
certain file would help me. I currently used find / nameoffile
to search for files or directories.
thanks

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
mailto:lists...@listserv.aol.com>>
with the body of "SIGNOFF AOLSERVER" in the email message. You
can leave the Subject: field of your email blank.



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
mailto:lists...@listserv.aol.com>> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.


-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the body of "SIGNOFF AOLSERVER" in the 
email message. You can leave the Subject: field of your email blank.





--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file

2009-06-26 Thread Dave Bauer 
On Fri, Jun 26, 2009 at 12:52 PM, Rusty Brooks  wrote:

> You can name config files for aolserver whatever you want, looks like this
> one is
> /opt/aolserver/servers/openacs/etc/config.tcl
> and it's probably serving pages out of something like
> /opt/aolserver/servers/openacs/pages/


Probably the pages are in /opt/aolserver/servers/openacs/www/

Of course OpenACS also has hundreds of dynamic pages generated under
openacs/packages/*

Dave


>
> although you can check the config.tcl script for the doc root.
>
> jon jon wrote:
>
>> When I do that command I get starting to read config file
>> Notice: nsd.tcl: using threadsafe tcl:
>> Notice: nsd.tcl: finished reading conig file.?
>> 1631 ?  Sl   0:28 /opt/aolserver/bin/nsd -it
>> /opt/aolserver/servers/openacs/etc/config.tcl -u pre-book -g prebook -b
>>  sorry I didn't post all of the output. The reason I was looking for this
>> file is to see what directory is serving out the webpages. I have never used
>> aolserver before, I am used to apache web server. isn't the config.tcl just
>>  a example config file for aolserver?
>> thanks
>>
>> On Fri, Jun 26, 2009 at 10:47 AM, Rusty Brooks > m...@rustybrooks.com>> wrote:
>>
>>Config files are all per-webserver so there may be more than one.
>>Typically they're supplied on the command line using the -t option
>>and you can sometimes get them with ps...
>>
>>ps ax | grep nsd
>> 3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
>> 9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
>>11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks
>>
>>The regular name is nsd.tcl but they can be called whatever you want.
>>
>>If ps doesn't give up teh command line, find out how they're getting
>>started and look for the -t option in there.
>>
>>jon jon wrote:
>>
>>Hi,
>>I am searching for the aolserver conifg file. I did not build
>>this server so aolserver is not installed in
>>usr/local/aolserver. The only thing I know is that I think
>>aolserver is installed in the opt directory. But  I don't know
>>what the config file is usually named for aolserver. The server
>>I am using is running fedora, so any help to find a name of a
>>certain file would help me. I currently used find / nameoffile
>>to search for files or directories.
>>thanks
>>
>>-- AOLserver - http://www.aolserver.com/
>>
>>To Remove yourself from this list, simply send an email to
>>mailto:lists...@listserv.aol.com>>
>>with the body of "SIGNOFF AOLSERVER" in the email message. You
>>can leave the Subject: field of your email blank.
>>
>>
>>
>>--
>>AOLserver - http://www.aolserver.com/
>>
>>To Remove yourself from this list, simply send an email to
>>mailto:lists...@listserv.aol.com>> with
>> the
>>body of "SIGNOFF AOLSERVER" in the email message. You can leave the
>>Subject: field of your email blank.
>>
>>
>> -- AOLserver - http://www.aolserver.com/
>>
>> To Remove yourself from this list, simply send an email to <
>> lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the
>> email message. You can leave the Subject: field of your email blank.
>>
>>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to <
> lists...@listserv.aol.com> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>



-- 
Dave Bauer
d...@solutiongrove.com
http://www.solutiongrove.com


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file

2009-06-26 Thread jon jon 
actually there is one file in
/opt/aolserver/servers/server1/pages
it is called index.adp

On Fri, Jun 26, 2009 at 11:52 AM, Rusty Brooks  wrote:

> You can name config files for aolserver whatever you want, looks like this
> one is
> /opt/aolserver/servers/openacs/etc/config.tcl
> and it's probably serving pages out of something like
> /opt/aolserver/servers/openacs/pages/
> although you can check the config.tcl script for the doc root.
>
> jon jon wrote:
>
>> When I do that command I get starting to read config file
>> Notice: nsd.tcl: using threadsafe tcl:
>> Notice: nsd.tcl: finished reading conig file.?
>> 1631 ?  Sl   0:28 /opt/aolserver/bin/nsd -it
>> /opt/aolserver/servers/openacs/etc/config.tcl -u pre-book -g prebook -b
>>  sorry I didn't post all of the output. The reason I was looking for this
>> file is to see what directory is serving out the webpages. I have never used
>> aolserver before, I am used to apache web server. isn't the config.tcl just
>>  a example config file for aolserver?
>> thanks
>>
>>  On Fri, Jun 26, 2009 at 10:47 AM, Rusty Brooks > m...@rustybrooks.com>> wrote:
>>
>>Config files are all per-webserver so there may be more than one.
>>Typically they're supplied on the command line using the -t option
>>and you can sometimes get them with ps...
>>
>>ps ax | grep nsd
>> 3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
>> 9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
>>11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t
>>/opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks
>>
>>The regular name is nsd.tcl but they can be called whatever you want.
>>
>>If ps doesn't give up teh command line, find out how they're getting
>>started and look for the -t option in there.
>>
>>jon jon wrote:
>>
>>Hi,
>>I am searching for the aolserver conifg file. I did not build
>>this server so aolserver is not installed in
>>usr/local/aolserver. The only thing I know is that I think
>>aolserver is installed in the opt directory. But  I don't know
>>what the config file is usually named for aolserver. The server
>>I am using is running fedora, so any help to find a name of a
>>certain file would help me. I currently used find / nameoffile
>>to search for files or directories.
>>thanks
>>
>>-- AOLserver - http://www.aolserver.com/
>>
>>To Remove yourself from this list, simply send an email to
>>mailto:lists...@listserv.aol.com>>
>>with the body of "SIGNOFF AOLSERVER" in the email message. You
>>can leave the Subject: field of your email blank.
>>
>>
>>
>>--
>>AOLserver - http://www.aolserver.com/
>>
>>To Remove yourself from this list, simply send an email to
>>mailto:lists...@listserv.aol.com>> with
>> the
>>body of "SIGNOFF AOLSERVER" in the email message. You can leave the
>>Subject: field of your email blank.
>>
>>
>> -- AOLserver - http://www.aolserver.com/
>>
>> To Remove yourself from this list, simply send an email to <
>> lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the
>> email message. You can leave the Subject: field of your email blank.
>>
>>
>
> --
>
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to <
> lists...@listserv.aol.com> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file

2009-06-26 Thread Rusty Brooks 
You can name config files for aolserver whatever you want, looks like 
this one is

/opt/aolserver/servers/openacs/etc/config.tcl
and it's probably serving pages out of something like
/opt/aolserver/servers/openacs/pages/
although you can check the config.tcl script for the doc root.

jon jon wrote:

When I do that command I get starting to read config file
Notice: nsd.tcl: using threadsafe tcl:
Notice: nsd.tcl: finished reading conig file.?
1631 ?  Sl   0:28 /opt/aolserver/bin/nsd -it 
/opt/aolserver/servers/openacs/etc/config.tcl -u pre-book -g prebook -b
 
sorry I didn't post all of the output. The reason I was looking for this 
file is to see what directory is serving out the webpages. I have never 
used aolserver before, I am used to apache web server. isn't the 
config.tcl just  a example config file for aolserver?

thanks

On Fri, Jun 26, 2009 at 10:47 AM, Rusty Brooks > wrote:


Config files are all per-webserver so there may be more than one.
Typically they're supplied on the command line using the -t option
and you can sometimes get them with ps...

ps ax | grep nsd
 3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
 9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t
/opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks

The regular name is nsd.tcl but they can be called whatever you want.

If ps doesn't give up teh command line, find out how they're getting
started and look for the -t option in there.

jon jon wrote:

Hi,
I am searching for the aolserver conifg file. I did not build
this server so aolserver is not installed in
usr/local/aolserver. The only thing I know is that I think
aolserver is installed in the opt directory. But  I don't know
what the config file is usually named for aolserver. The server
I am using is running fedora, so any help to find a name of a
certain file would help me. I currently used find / nameoffile
to search for files or directories.
thanks

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
mailto:lists...@listserv.aol.com>>
with the body of "SIGNOFF AOLSERVER" in the email message. You
can leave the Subject: field of your email blank.



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
mailto:lists...@listserv.aol.com>> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.


-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the body of "SIGNOFF AOLSERVER" in the 
email message. You can leave the Subject: field of your email blank.





--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file

2009-06-26 Thread jon jon 
When I do that command I get starting to read config file
Notice: nsd.tcl: using threadsafe tcl:
Notice: nsd.tcl: finished reading conig file.?
1631 ?  Sl   0:28 /opt/aolserver/bin/nsd -it
/opt/aolserver/servers/openacs/etc/config.tcl -u pre-book -g prebook -b

sorry I didn't post all of the output. The reason I was looking for this
file is to see what directory is serving out the webpages. I have never used
aolserver before, I am used to apache web server. isn't the config.tcl just
a example config file for aolserver?
thanks

On Fri, Jun 26, 2009 at 10:47 AM, Rusty Brooks  wrote:

> Config files are all per-webserver so there may be more than one. Typically
> they're supplied on the command line using the -t option and you can
> sometimes get them with ps...
>
> ps ax | grep nsd
>  3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t
> /opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
>  9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t
> /opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
> 11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t
> /opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks
>
> The regular name is nsd.tcl but they can be called whatever you want.
>
> If ps doesn't give up teh command line, find out how they're getting
> started and look for the -t option in there.
>
> jon jon wrote:
>
>>  Hi,
>> I am searching for the aolserver conifg file. I did not build this server
>> so aolserver is not installed in usr/local/aolserver. The only thing I know
>> is that I think aolserver is installed in the opt directory. But  I don't
>> know what the config file is usually named for aolserver. The server I am
>> using is running fedora, so any help to find a name of a certain file would
>> help me. I currently used find / nameoffile to search for files or
>> directories.
>> thanks
>>
>> -- AOLserver - http://www.aolserver.com/
>>
>> To Remove yourself from this list, simply send an email to <
>> lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the
>> email message. You can leave the Subject: field of your email blank.
>>
>>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to <
> lists...@listserv.aol.com> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file

2009-06-26 Thread Rusty Brooks 
Config files are all per-webserver so there may be more than one. 
Typically they're supplied on the command line using the -t option and 
you can sometimes get them with ps...


ps ax | grep nsd
 3182 ?Ssl0:05 /opt/AOLServer/bin/nsd -b * -t 
/opt/AOLServer/servers/riddell.test/nsd.tcl.riddell.test -u rbrooks
 9492 ?Ssl   30:02 /opt/AOLServer/bin/nsd -b * -t 
/opt/AOLServer/servers/riddell/nsd.tcl.riddell -u riddell
11426 ?Ssl0:31 /opt/AOLServer/bin/nsd -b * -t 
/opt/AOLServer/servers/studhudimo/nsd.tcl.studhudimo -u rbrooks


The regular name is nsd.tcl but they can be called whatever you want.

If ps doesn't give up teh command line, find out how they're getting 
started and look for the -t option in there.


jon jon wrote:

Hi,
I am searching for the aolserver conifg file. I did not build this 
server so aolserver is not installed in usr/local/aolserver. The only 
thing I know is that I think aolserver is installed in the opt 
directory. But  I don't know what the config file is usually named for 
aolserver. The server I am using is running fedora, so any help to find 
a name of a certain file would help me. I currently used find / 
nameoffile to search for files or directories.

thanks

-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the body of "SIGNOFF AOLSERVER" in the 
email message. You can leave the Subject: field of your email blank.





--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
 with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file example of multihome config?

2006-04-30 Thread John Buckman 

On Apr 30, 2006, at 10:46 AM, Tom Jackson wrote:


John,

Here is an example which covers virtual servers using multiple  
nssocks,

and the same nssock for multiple virtual servers.



There is a static config at the top of
,
generated from the example.


Perfect, thank you! Clearly, one of the key ideas is multiple sock  
modules, as you have:


ns_section ns/modules
ns_param nssock0 /web/m2/bin/nssock.so
ns_param nssock2 /web/m2/bin/nssock.so
ns_param nssock3 /web/m2/bin/nssock.so

-john


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file example of multihome config?

2006-04-30 Thread Tom Jackson 
John,

Here is an example which covers virtual servers using multiple nssocks,
and the same nssock for multiple virtual servers.



There is a static config at the top of 
, 
generated from the example.

tom jackson


On Saturday 29 April 2006 15:42, John Buckman wrote:
> I'm struggling to configure AOLserver to support multiple web sites,
> with independent TCP/IP addresses.
>
> Can someone attach a config file example of multihoming?
>
> The config file seems to support it, but there are both server-
> specific and global mentions of TCP/IP address and port #, so it's
> quite unclear how to transfer the sample config file into one that's
> multihome capable.
>
> -john
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the
> email message. You can leave the Subject: field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file example of multihome config?

2006-04-30 Thread dhogaza 
> What I'm looking to do is have multiple $servers in one aolserver
> process
>
> Iie: host several unrelated web sites with one aolserver process.
>
> Doable? Config example?

Here's the wiki entry on virtual hosting:

http://panoptic.com/wiki/aolserver/Virtual_Hosting

That example is for multiple servers on a single IP.  Since you've figured
out how to listen to multiple IPs you should be able to figure out how to
bind them to different virtual servers ...

Post a working example when you have one and ... add it to the wiki!


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file example of multihome config?

2006-04-30 Thread John Buckman 

On Apr 30, 2006, at 12:57 AM, Wojciech Kocjan wrote:


Dnia 30-04-2006 o 00:42:30 John Buckman <[EMAIL PROTECTED]> napisał:
I'm struggling to configure AOLserver to support multiple web  
sites, with independent TCP/IP addresses.


Can someone attach a config file example of multihoming?

The config file seems to support it, but there are both server- 
specific and global mentions of TCP/IP address and port #, so it's  
quite unclear how to transfer the sample config file into one  
that's multihome capable.


Notice you need to specify nssock multiple times and you need to  
configure each of it's instances.


The config file below seems to be to get one $server instance to  
listen to multiple IP addresses.


What I'm looking to do is have multiple $servers in one aolserver  
process


Iie: host several unrelated web sites with one aolserver process.

Doable? Config example?

-john




ns_section  "ns/server/$server/modules"
ns_param"nssock1"   "nssock.so"
ns_param"nssock2"   "nssock.so"


ns_section  "ns/server/$server/module/nssock1"
ns_param"Port"  "80"
ns_param"Hostname"  "www1.something.com"
ns_param"Address"   "10.0.0.1"

ns_section  "ns/server/$server/module/nssock2"
ns_param"Port"  "80"
ns_param"Hostname"  "www2.something.com"
ns_param"Address"   "10.0.0.2"

Of course ports may also differ.

--
Wojciech Kocjan
[EMAIL PROTECTED]


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to  
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the  
Subject: field of your email blank.



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] config file example of multihome config?

2006-04-30 Thread Wojciech Kocjan 

Dnia 30-04-2006 o 00:42:30 John Buckman <[EMAIL PROTECTED]> napisał:
I'm struggling to configure AOLserver to support multiple web sites,  
with independent TCP/IP addresses.


Can someone attach a config file example of multihoming?

The config file seems to support it, but there are both server-specific  
and global mentions of TCP/IP address and port #, so it's quite unclear  
how to transfer the sample config file into one that's multihome capable.


Notice you need to specify nssock multiple times and you need to configure  
each of it's instances.


ns_section  "ns/server/$server/modules"
ns_param"nssock1"   "nssock.so"
ns_param"nssock2"   "nssock.so"


ns_section  "ns/server/$server/module/nssock1"
ns_param"Port"  "80"
ns_param"Hostname"  "www1.something.com"
ns_param"Address"   "10.0.0.1"

ns_section  "ns/server/$server/module/nssock2"
ns_param"Port"  "80"
ns_param"Hostname"  "www2.something.com"
ns_param"Address"   "10.0.0.2"

Of course ports may also differ.

--
Wojciech Kocjan
[EMAIL PROTECTED]


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Re: [AOLSERVER] Config File Improvements

2002-12-03 Thread Nathan Folkman 
In a message dated 12/3/2002 3:39:12 PM Eastern Standard Time, [EMAIL PROTECTED] writes:

I would like to work on this,  I have already collected the config
parameters for the ftp module, but I don't know the effect of all of
them. If anyone has other module config parameter settings, I would like
to start with a single file that lists them all, then others can look
and see if anything is missing. The job of creating a different file
arrangement should at least be left until we have a complete list.
Maybe the old 2.3.3 docs have info on older modules as well.


Great! Thanks for offering to help - I'll add this as a task in the SF task manager. Unfortuneatly the best tool you've got to determine all of the configuration options is probably going to be grep. I'd also limit the sample-config.tcl to core AOLserver modules.

cd $TOP/aolserver
find . \( -name '*.c' -o -name '*.cpp' \) | xargs grep "Ns_Config"

- Nathan

Re: [AOLSERVER] Config File Improvements

2002-12-03 Thread Tom Jackson 
Nathan Folkman wrote:



That said, I'd recommend sticking with a single default
sample-config.tcl for now. Is there anyone who would be interested in
signing up to work on better documentation of the various
configuration options? This work will need to be done for both the
3.5.x and 4.0 versions since there are some pretty significant
differences in 4.0 (virtual servers, configurable thread pools, etc.)
Let me know!


I would like to work on this,  I have already collected the config
parameters for the ftp module, but I don't know the effect of all of
them. If anyone has other module config parameter settings, I would like
to start with a single file that lists them all, then others can look
and see if anything is missing. The job of creating a different file
arrangement should at least be left until we have a complete list.
Maybe the old 2.3.3 docs have info on older modules as well.

--Tom Jackson

Re: [AOLSERVER] Config File Improvements

2002-12-03 Thread Nathan Folkman 
In a message dated 12/3/2002 2:31:37 PM Eastern Standard Time, [EMAIL PROTECTED] writes:

Has anyone worked on improving the default nsd.tcl file structure? For
new users, and for users wanting to try something new, the lack of
documentation and default values for the different modules makes
experimentation difficult.
So here are some random thoughts:
Move module configuration into separate files. Handle all explaination
and variable setting at the top of these files, source the module file
iff it is actually used in the main nsd.tcl file.

Or do the same with a single file, but enclose the module sections
inside ifs conditioned on whether the module is used.

My overall impression is that some solution that allowed the developer
to concentrate on the top part of the file for setting well named, and
maybe commented, variables would be much easier to setup and maintain.


Good ideas, but I'd recommend keeping the default configuration file a single file in order to keep things simple. The hierarchical structure of the configuration sections was designed to help keep things clear. We can certainly improve the documentation that is provided, and extend it to include all the parameters and better explanations of what each is used for. I'd recommend that module writers include configuration examples in a README file which they include.

Having Tcl based configuration files is very powerful, and allows you to do many clever things, but can also quickly lead to overly complicated configuration. I'm currently faced with cleaning up such a mess myself.

That said, I'd recommend sticking with a single default sample-config.tcl for now. Is there anyone who would be interested in signing up to work on better documentation of the various configuration options? This work will need to be done for both the 3.5.x and 4.0 versions since there are some pretty significant differences in 4.0 (virtual servers, configurable thread pools, etc.) Let me know!

- Nathan

Re: [AOLSERVER] Config File Improvements

2002-12-03 Thread Scott S. Goodwin 
The AOLserver test platform I'm building already does this for tests. When I
build the platform with nsopenssl, the $TOP/tests/nsopenssl.tcl file is set
up. The nsd.tcl file looks in $TOP/tests for module config files and loads
the ones it finds. It also loads the .so files for modules that have a .tcl
file in the tests directory.

To make this a feature of AOLserver in general, the following will need to
be done:

1. Put the module config Tcl files in a more sane place. Somewhere under
servers/$servername makes sense since AOLserver 4.x will be virtual server
capable, and you'll probably want a separate config file for each module on
a per-virtual server basis. Module dependencies would also need to be
handled as some modules may need to be loaded prior to others.

2. The main nsd.tcl file will need to be altered such that it only contains
the global server config params and a looping construct to start and
configure each virtual server and configure the modules for each of those
servers. The issue here is that only one copy of each module should
(probably) be loaded regardless of how many virtual servers are defined.
This means that each module will probably need to recognize what server+conn
context it's in when it is being configured and when it performs a requested
operation. nsopenssl, for example, will need to know what virtual server
owns port 443 versus port 8443 and do the right thing (i.e. use different
certs for the two ports).

I would expect each module that compiled would install its own default init
Tcl file into the right place, which the admin would then alter to suit
their system.

/s.


- Original Message -
From: "Tom Jackson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 03, 2002 1:30 PM
Subject: [AOLSERVER] Config File Improvements


> Has anyone worked on improving the default nsd.tcl file structure? For
> new users, and for users wanting to try something new, the lack of
> documentation and default values for the different modules makes
> experimentation difficult.
> So here are some random thoughts:
> Move module configuration into separate files. Handle all explaination
> and variable setting at the top of these files, source the module file
> iff it is actually used in the main nsd.tcl file.
>
> Or do the same with a single file, but enclose the module sections
> inside ifs conditioned on whether the module is used.
>
> My overall impression is that some solution that allowed the developer
> to concentrate on the top part of the file for setting well named, and
> maybe commented, variables would be much easier to setup and maintain.
>
> --Tom Jackson
>
>

Re: [AOLSERVER] Config File Improvements

2002-12-03 Thread Jim Wilcoxson 
Here's an idea: make a directory like "config" for the nsd stuff.
Have a main file there, plus a bunch of module config files.  All of
the module config files get sourced by a loop in the main file.  This
would eliminate having to list the modules in the main file and also
have a config section for them.  To delete a module, rename the config
file. To add a module, copy in the config file, or touch it to create
an empty config file.  It would also let developers publish config
files for their modules/extensions, if required.

One specific area that is clumsy for us is IP aliases.  It'd be nice
to say in 1 line:

ipalias xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx:8080 xxx.xxx.xxx.xxx

Doing that with the nssock config directives is messy.

Jim


> Has anyone worked on improving the default nsd.tcl file structure? For
> new users, and for users wanting to try something new, the lack of
> documentation and default values for the different modules makes
> experimentation difficult.
> So here are some random thoughts:
> Move module configuration into separate files. Handle all explaination
> and variable setting at the top of these files, source the module file
> iff it is actually used in the main nsd.tcl file.
>
> Or do the same with a single file, but enclose the module sections
> inside ifs conditioned on whether the module is used.
>
> My overall impression is that some solution that allowed the developer
> to concentrate on the top part of the file for setting well named, and
> maybe commented, variables would be much easier to setup and maintain.
>
> --Tom Jackson
>