Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

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

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

Print Reply
Subject:
Re: Synchronization problem with LISTSERV 1.8d on HP-UX 10.20
From:
Valdis Kletnieks <[log in to unmask]>
Reply To:
LISTSERV give-and-take forum <[log in to unmask]>
Date:
Thu, 3 Feb 2000 10:50:52 -0500
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (1203 bytes) , application/pgp-signature (291 bytes)
On Wed, 02 Feb 2000 19:27:20 EST, John Lyon <[log in to unmask]>  said:
> in the same message is beyond me. My guess is the problem with your way
> to do this has to do with Listserv trying to process two (or more) conflicting
> commands in the same message. At times when Listserv is busy it may be
> still trying to GET and LOCK the list while it trys to execute the UNLOCK
> command. This is why the commnds don't always yeild the same results in
> the order they were given. I'm sure Lsoft discovered this long ago and why
> this method is not recommended.

This implies that Listserv is a lot more multithreaded than it actually is.

Hint: Look at the console log - do you *ever* see console messages for two
commands intermixed?

The *real* reason Lsoft doesn't recommend this is because the list owner
*will* forget to send the UNLOCK, or they'll send it to the wrong place, or
their mail server will lose it, or...  Every once in a while, I'll come across
one of our lists that's been locked for months just because the list owner
messed up and didn't say 'NOLOCK'.

--
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech



ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV