home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!network.ucsd.edu!mvb.saic.com!mx-list
- From: Hunter Goatley <goathunter@WKUVX1.BITNET>
- Newsgroups: vmsnet.mail.mx
- Subject: RE: A question and an enhancement request.
- Message-ID: <0095DFEB.8B9CB7A0.2279@WKUVX1.BITNET>
- Date: Thu, 23 Jul 1992 08:37:08 EDT
- Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 29
-
- "Brian Tillman, Smiths Industries, VAX Support, x8425" writes:
- >
- >>My system is what I consider busy (typically over 1000 messages a day) and
- >>I don't recall seeing this problem. I seem to recall that ONCE I got
- >>a 'currently locked' error from FLQU SHOW but other than that I don't
- >>see locks. CPU speed may have a lot to do with it - MX runs on an 8820
- >>here (though sometimes at priority 1 - ouch!)
- >
- [...]
- >John, if you still use FLQU, then you must still be using V2.x. Perhaps this
- >problem didn't exist in versions prior to V3.x (we're using V3.1C).
- >
- >At any rate, thanks for the comments.
- >
- >If anyone else can comment on incoming mail locking SYSTEM_QUEUE.FLQ_CTL in suc
- h
- >a way as to elicit file locked errors from VMS mail when trying to *send* using
- >MX% as the transport, please comment as well.
- >
- In all the time I've been using MX, I've seen what you're describing
- once or twice. MX here processes well over 2000 messages a day and
- I've never heard of a user complaining about this problem. In fact, I
- haven't seen it since v2.x, so I'm not sure what to tell you. Maybe
- Matt has some ideas?
-
- Hunter
- ------
- Hunter Goatley, VMS Systems Programmer, Western Kentucky University
- goathunter@WKUVX1.BITNET, 502-745-5251
-