on a per-dir or per-filespec basis.  Allowed keys are:
ErrorDirectory	- Changes the dir error pages are served from
CGIDirectory	- Changes the CGIDorectory value
ARS		- ARS required for this resource (Overrides access.ars)
Realm		- Authentication realm name to send to remote

Filespecs are the section name and the first match wins.  So:
[*.cgi]
Realm=CGI Scripts

[*.*]
ARS=Level 90

Would mean that for CGI scripts, the ARS would not apply.

And:
[*.*]
ARS Level 90

[*.cgi]
Realm=CGI Scripts

Would never set the Realm name.

fname against the filespec spec, not allowing * to match the path delimiter
if path is TRUE.

(e.g. "CRIT" instead of "CRITICAL").

section) or per service, using the LogLevel key (default value: LOG_DEBUG).
This commit requires an xpdev/ini_file.* update.

filtering by log level by sysop configuration.

(should LOG_INFO be the only abbreviated string?).

mail.sid corruption (blocks of records getting zero'd out).

like that.

execution while using chunked transfer coding.

Assumes that JS_DestroyIdArray(session->js_cx, heads); actually removes
everything from the array.

the SSJS script is sent immediately, and the keep-alvie session is maintained.
chunked mode is ONLY sent to HTTP/1.1 clients, and is preferred over fast mode.

This means fast mode is now only usefull for HTTP/1.0 and HTTP/0.9 requests.

Still need to do chunked support for CGI scripts though.

Directions on forcing call-out events.

BCC only currently... need to look into MSVC methods to handle this
properly.

pthread + signals doesn't work correctly.
Loop on the select forever erm... forever.
ie: select() forever forever now.

startup iser (often root)

      You do NOT need to install the termcap-compat package.  If termcap
      isn't installed, it means nothing uses it.  Only if there is a
      termcap do you need to add the ansi-bbs termcap definition.

processes environment block when adding new environment strings, otherwise,
existing values (for say "SBBSNODE") would not be over-ridden.

distros.