 
Sun, 24 May 1992 15:34:54 EDT
|
>PUTting a List Header
>Date: Tue, 19 May 1992 19:16:11 PST
>From: "Patricia Parker" <[log in to unmask]>
>
>I got a list header. I changed it and sent it back successfully with
>LSVPUT. [. . .]
Woah. LSVPUT *works*? Since when? When I tried to use it about
six months ago, it never worked. I talked to the CIS staff at my school
(Brown University) when first trying to put to the fileserver, and they
didn't know what to tell me once we established that LSVPUT didn't work.
Finally, we ended up hacking and found how to "put" manually.
Below is the header of the LSVPUT exec I/we used back then. If it
has been updated since, please let me know and send me/us a copy so that
other listowners here can use it.
Thanks.
-- Steven Feldman <[log in to unmask]>
+ + + + + + +
/***********************************************************************
* *
* LSVPUT -- Program to issue a PUT command to Listserv *
* *
* Copyright (c) Eric Thomas 1986,1988 <[log in to unmask]> *
* (c) Harold Pritchett 1986 (HAROLD at UGA) *
* *
* This file was last updated on Tuesday, October the 4th of 1988 *
* *
* Updates to the code 11/25/88 by Christian Reichetzeder are *
* marked with *+* in the line or at begin and end of blocks. *
* *
* This program assists you in sending a PUT command to Listserv. It *
* will automatically build a work file with the required password *
* inserted on top of it and send it to the LISTSERV server. *
* *
* *
* The syntax of the LSVPUT command is: *
* *
* LSVPUT <fn <ft <fm>>> <(options> *
* LIST * *
* *
* Valid options are: NEWPW PURGE TO *
* CReate List *
* DELete PUT PUTC *
* NODIST *
* FIlelist filelist *
* OLDDate *
* CKDATE *
* TITle title *
* *
* The following options are valid in any context: *
* *
* TO nickname | nodeid: identifies the server to send the file to *
* *
* NEWPW: indicates you want LSVPUT to prompt you to enter the pro- *
* per password(s) regardless of them being in your GLOBALV *
* file or not. Use this option when you have changed the *
* corresponding password. *
* *
* PURGE: orders LSVPUT to forget all the passwords, userid/node *
* pairs, defaults settings, etc. This is equivalent to a *
* GLOBALV PURGE of all LSVPUT variables. *
* *
* *
* The following options are valid only when a list is being stored: *
* *
* CReate: indicates that you are creating a new list and that the *
* "createpw" should be used to send the list. It will not *
* be recorded as being the list password. This option is *
* for postmasters use only. *
* *
* List: indicates that the file being sent is a list, with the *
* filename being the listname and the filetype being the *
* node to which the list is to be sent. When the filetype *
* of a file is 'LIST', the List option is forced with the *
* host server being the local (ie default) server. *
* *
* *
* The following options are valid only when files are being stored: *
* *
* DELete: indicates that you want to delete the file from the *
* server. *
* *
* PUTC: indicates that a PUTC function is to be performed, ie the *
* file must be stored on one of the server's system disks. *
* This option is restricted to postmasters who know their *
* server's "storepw". *
* *
* PUT: indicates that a PUT function is to be performed. This *
* option is restricted to list owners and file owners. *
* *
*> The PUT command is supported since release 1.5f; FILELISTs *
*> can also be PUT (since release 1.5j). *
* *
*+* FIlelist filelist: to specify the FILELIST, forces PUT *
*+* OLDDATE *
*+* CKDATE *
*+* TITLE: everything after this keyword is taken as title. *
*+* must be the last option on the line *
* *
* You will be prompted for all the keywords that you have omitted. *
* *
***********************************************************************/
|
|
|
