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:
brain check on GET LOG
From:
Nick Laflamme <[log in to unmask]>
Reply To:
Forum on LISTSERV release 1.6
Date:
Thu, 3 May 90 09:32:00 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
I've noticed a few times while retrieving LOG files of distribution
lists that some LISTSERVs try not to pump more than 256K to any one
user any one day.  That seems reasonable.
 
I just had a GET of a log file rejected because the single log file
exceeds 256K!  What good is a log file I can't GET?
 
I realize it's useful for local reading (LINK and read without a GET),
and I realize this logic is a local user exit that any LISTSERV
maintainer can modify to her heart's content.
 
All I'm asking is, let's check for common sense on these exits, ok?
(The alternative would be automatically starting a second log file
when one is too large, but that depends on a uniform definition of
"too large".)
 
I'll get off my soapbox now....
 
Nick

ATOM RSS1 RSS2

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