LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sun, 6 Oct 1996 23:51:44 -0500
TEXT/PLAIN (49 lines)
> When you put the list. The line PUT PANAFARICA.LIST LIST PW=XXXXXX is
> already added at the top. You must change the XXXXX for the current list
 
Unless Eric (Thomas) has changed it again this won't work if you GET the
entire list, only if you GET the list header (and maybe you need nolock).
Eric took it out a couple of years ago as a security measure to help keep
newbie owners from accidentally wiping their lists (used to come with
ANY "get listaname" command).  Argued with him on this list and he agreed
to put it back for   get listname (head nol pw=xxxxxxxxx
which was what I wanted.  Anyway, if you do a    get listname
you may not have the handy, preinstalled PUT line.
 
> password. The previous owner should tell you what the list password is.
 
In a number of years of mucking about with LISTERV lists I have never
needed the list password (my lists don't even have list passwords,
far as I know).  I use my personal LISTSERV password, which is more
flexible, as I understand it.
 
> Otherwise follow LISTSERV instruction and add your own ppassword.
> Remember that the list is "locked" if the put did not went through (No
 
To lock or not to lock, that is the question.  If you really need, and
want, to mess with the entire list, probably a good idea (it's the
default if you don't specify otherwise).  If you are just going to make
a few changes to the header nolock may be better
get listname (head nol pw=xxxxxxxx
 
If you are dealing with the entire list, not just the header, you will
want the list locked (you don't have to give a special option for that),
as, if you make changes to the list itself without locking it and then
put the list back you will wipe out any new subscriptions which came in
in the interim.  99% of all listowners (including myself) have no business
trying to get, modify and put the full list.  Get it just to scan for
info, yeah, in which case one uses nolock.
 
On the header there is no reason that I see not to use nolock.  This does,
though, assume, that you are the sole listowner or, if you have several
listowners, everyone understands that *you* take care of the list header
and no one else touches it.  If there is a possibilty that some other
listowner might try to change the header, certainly lock the list while
you are working on it.
 
I always use nolock, but then I have trained co-owners to leave all that
stuff to me.  Makes things much simpler and generally they are glad not
to have to muck with it.
 
Douglas

ATOM RSS1 RSS2