Hi Mike,
> ns_section "ns/server/server1/pool/fast"
> should probably be
> ns_section "ns/server/${servername}/pool/fast"
thats true.
> mimetypes.tcl is not sourced
the binary has a lot of types compiled for the start, see nsd/mimetypes.c.
the "mimetypes.tcl" from the contrib dir can be optionally sourced.
> nscp and nsadmin are enabled by default with known passwords?
yes, should be changed, imho.
> it's also almost entirely unclear which modules are needed/do what...
usually you should be fine with nssock and nslog. the others could be
commented out.
> perhaps tcl/ directory is always sourced in its entirety - but then
> what are "Tcl modules" mentioned in sample config?
There is the private (per-virtual-server) Tcl modules directory
ns_section "ns/server/servername/tcl"
ns_param library PATH/modules/tcl
The [ns_library private] command will return that.
Shared modules are returned via [ns_library shared] and configured:
ns_section "ns/parameters"
ns_param tcllibrary PATH/tcl
The mentioned "Tcl modules" are loaded via 'ns_ictl addmodule' (for
virtual-servers), but others may comment why this was implemented.
> It would be amazingly useful if the configuration section of the wiki
> was available or at least some pointer to another document existed
> somewhere...
i'm currently experimenting with a layout like this:
# Logical configuration units are separated into different sub-configuration
# files and included here.
#
# Legend: (c) change before first use
#
# nsd.conf
# |
# |-- global.conf (c)
# |-- uid.conf (c)
# |-- listen.conf (c)
# |-- server-tuning.conf
# |-- server-log.conf
# |-- access-log.conf
# |-- mimetypes.conf
# |-- i18l.conf
# |-- adp.conf
# |-- smtp.conf
# |-- database.conf
# |-- modules.conf
# |-- file-caching.conf
# |-- control-port.conf
# |-- statistics.conf
# |-- cgi.conf
# |
# `--modules.d/
# `-- *.conf
# `--vhosts.d/
# `-- *.conf (c)
"experimenting", because there's no perfect one-layout-fits-it-all approach
and sometimes separation is not that logical.
(this one, e.g., may come out to be annoying for someone using lots of virtual
hosting (i don't, so it's no problem for me ;-)) as i don't know if you can
encapsulate most of the configs to a separate file without breaking the basic
concept.)
Bernd.
