Path: utzoo!attcan!ncrcan!scocan!david
From: david@sco.COM (David J. Fiander)
Newsgroups: comp.unix.sysv386
Subject: MMDF lock directory (was Re: '386 Unix Wars)
Keywords: not a bug, but an incredible simulation!
Message-ID: <1991Jan07.204046.3668@sco.COM>
Date: 7 Jan 91 20:40:46 GMT
References: <1991Jan1.025724.25700@NCoast.ORG> <188@raysnec.UUCP> <1991Jan4.032920.13524@NCoast.ORG>
Sender: news@sco.COM (News administration)
Organization: SCO Canada, Inc.
Lines: 27

In article <1991Jan4.032920.13524@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
>I had this happen to me once as well... but when I ran checkque as root
>instead of mmdf, I saw stuff in the queue.  Red flag... I immediately ran
>checkup and it straightened out permissions for me.  And pointed out the only
>bug I've found in MMDFIIb #43 to date:  you can't change the lock directory in
>mmdftailor, it gets misread.  Since I've got the source, if it annoys me
>enough I'll track it down and fix it.
>

Brandon, in the introduction to the section on runtime tailoring of MMDF in the 
paper "Installing and Operating MMDF II" (which I know you have, since you have
told others where to get it), it mentions that strings which are not simply 
alpha-numeric should be quoted.  If you do this it will quite successfully read
the lock directory name from mmdftailor.  I was bitten by this once when I 
tried to put an absolute pathname into the tailor file to log debugging output
for one particular channel.

>++Brandon
>-- 
>Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
>Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
>America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
>uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY

David J. Fiander
MMDF Development Team
SCO Canada