home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!ames!network.ucsd.edu!mvb.saic.com!mx-list
- From: "John F. Sandhoff" <syssand@CCVAX.CCS.CSUS.EDU>
- Newsgroups: vmsnet.mail.mx
- Subject: RE: A question and an enhancement request.
- Message-ID: <0095DF67.8F00AF20.23290@CCVAX.CCS.CSUS.EDU>
- Date: Wed, 22 Jul 1992 16:52:20 PDT
- Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 29
-
-
- > The question is this: is it typical for MX to lock the SYSTEM_QUEUE.FLQ_CTL
- > file when it is receiving mail?
-
- 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!)
-
- > My enhancement request is that MX open the log files differently, like VMS
- > opens log files, so that one can TYPE the current log file...
-
- Yes, frustrating. There's a workaround if you really want to see
- the file:
-
- $ BACKUP/IGNORE=INTERLOCK MX_LOCAL_DIR:MX_LOCAL_NODE1.LOG FOOLOG.LOG
- $ TYPE/PAGE FOOLOG.LOG
- $ DELETE/ERASE FOOLOG.LOG
-
- Be *sure* you're careful with the output file spec so you don't clobber
- a real log file :-)
-
- Note: requires SYSPRV to work. We all have that, right? :-)
-
- John F. Sandhoff, University Network Support
- California State University, Sacramento - USA
- sandhoff@csus.edu
-
-