Subject: | |
From: | |
Reply To: | |
Date: | Tue, 27 Apr 1999 19:40:09 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Well, maybe you can answer this one that I posted to the list owner's forum:
All of the lists on my server show an incorrect URL for the web archives.
For example the index page is listed as:
http://listserv.regionofdoom.com/archives/index.html
When it should really be:
http://listserv.regionofdoom.com/listserv/index.html
I know it is pulling that from my system, but from where? I'd like to
correct that. Haven't had much luck finding it yet...still looking...
In the site.cfg it the following settings are:
WWW_ARCHIVE_CGI=http://listserv.regionofdoom.com/cgi-bin/wa.exe
WWW_ARCHIVE_DIR=C:\InetPub\wwwroot\LISTSERV
Both of these are correct paths...unless maybe they conflict with some other
setting elsewhere?
Does ListServ just not want it in a directory other than archive? I suppose
I can move it back, but I would think that it would be less work to keep it
where it is and modify some setting somewhere.
Ken Pauley
-----Original Message-----
From: Ben Parker [mailto:[log in to unmask]]
Sent: Tuesday, April 27, 1999 3:41 PM
To: [log in to unmask]
Subject: Re: Does LISTSERV WWW Interface support archives in
subdirectories?
On Tue, 27 Apr 1999 17:43:47 -0400, Paul Franco <[log in to unmask]>
wrote:
>Does LISTSERV WWW Interface support archives in subdirectories?
>
LISTSERV and the wa* cgi do not support heirarchical subdirs in the archive
indexes. i.e.
+wwwwroot
|
+--+archives
|
+ listname1_dir
+ listname2_dir
+ etc
all the listname subdirs must be on the same 'level', 1 under the archives
dir.
which is one under the wwwroot dir.
Note that the only thing that should be in these directories is the index
files
pointing to the actual message logfiles (listname.logyymm) which should be
elsewhere, preferably under the /home/listserv/lists/ tree. Doing so
automatically handles all necessary permissions. message log files (created
and
written by LISTSERV) are already in its tree. message index files (used by
wa*)
are under it's tree and no writing occurs there by wa* so security cannot be
compromised.
|
|
|