On Wed, 2 Sep 1992 10:56:48 CST you said:
>From:  Adam Floro
>First of all, I am trying to 'get' LSVPUT EXEC from LISTSERV
>and it won't send it to me.  LISTSERV says LSVPUT EXEC is
>unknown.  What's wrong?  Should I add this to a FILELIST
>such as TOOLS FILELIST?
 
That is the correct behavior, since LSVPUT is not found in any of the default
FILEIDs for the standard filelists. The only way to get LSVPUT, hence, is by
accesing a Listserv 191 minidisk and sending/copying the file.
 
You should not modify the default (standard) filelists at all. These are
INFO, CONTROL and TOOLS. LISTSERV FILELIST needs to be modified when you
want to add a new filelist to your server only.
 
>I'm also trying to get and put LOCAL SYSVARS and that will
>not work either.  Presumably for the same reasons as the
>above problem.  Any ideas?
 
I can only assume that Eric deliberately excluded these files from the
standard filelists for security reasons. Given the sensitive nature of all
the SYSVARS files, the safest route is to log onto the server's console.
 
>  MDISK.200 = '* N W L 85 95 //200: public file library.'
>  CHECKMDISK = CHECKMDISK '200'
>
>We told LISTSERV to link to 200, did a STOP REBOOT, and then
>a QUERY DISK, and there's no 200 disk accessed.  Ben, are
>you listening?  Any ideas on this one?
 
Working perfectly well.
 
You have told the MDISK code that the 200 minidisk is to be dynamically
accessed. So, after the startup verification, the minidisk is NOT accessed
until it is really needed. If you want QUERY DISK to see it, do an operation
that puts/gets info on that disk and THEN run QUERY.
 
Did ya check the server's console when it restarted ? The MDISK code will have
displayed the current state of all the minidisks, including those with
dynamic access.
 
>I seem to be missing some of the documents and need to retrieve
>the rest.  Where are they?
 
Recalling (from memory) one of the various info files I received when
I did my latest LISTSERV installation, "what you see is what you get..."
In other words, much of the listed documentation was planned but never
written. One of the reasons why Listserv maintenance is still somewhat of
a black art, including a good dose of obscure and mysterious (to the
uninitiated) incantations.... ;)
>
Relax; the code is well behaved  and all the commands are really logical,
once you get to know them.
>Southern Illinois University                  IP:  [log in to unmask]
JMC