home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!noiro.acs.uci.edu!unogate!mvb.saic.com!mx-list
- From: "Brian Tillman, Smiths Industries, VAX Support, x8425"
- Newsgroups: vmsnet.mail.mx
- Subject: RE: A question and an enhancement request.
- Message-ID: <0095DFEE.3D3CE820.8428@swdev.si.com>
- Date: Thu, 23 Jul 1992 08:56:24 EDT
- Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 29
-
- John F. Sandhoff (sandhoff@csus.edu) 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!)
-
- Well, we use MX a *whole* lot less (about six people) and it's happened twice in
- the past month. Now, that may seem very little, but it seems that if we release
- MX to all 500 of our accounts, we could very well see this much more frequently.
- This would mark MX in the minds of the Email people here as a flawed product and
- we would be forced to use our previous SMTP mailer (yuck!).
-
- 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 such
- a way as to elicit file locked errors from VMS mail when trying to *send* using
- MX% as the transport, please comment as well.
-
- -----------------------------+--------------------------------
- Brian Tillman | Internet: tillman@swdev.si.com
- Smiths Industries, Inc. |
- 4141 Eastern Ave. MS129 | Hey, I said this stuff myself.
- Grand Rapids, MI 49518-8727 | My company has no part in it.
- -----------------------------+--------------------------------
-