Great Circle Associates Majordomo-Workers
(January 1998)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: The majordomo log file... (1.94.4) two items
From: Dave Wolfe <dwolfe @ risc . sps . mot . com>
Date: Tue, 20 Jan 1998 10:59:40 -0600 (CST)
To: dmbong @ commline . com (Brian L. Heess)
Cc: majordomo-workers @ GreatCircle . COM
In-reply-to: <Pine.BSF.3.96.980120110928.22416D-100000@krumm.commline.com> from "Brian L. Heess" at Jan 20, 98 11:11:03 am

[ Brian L. Heess writes: ]
> 
> On Tue, 20 Jan 1998, Dave Wolfe wrote:
> 
> > What version did you upgrade from??? The primary reason for all time has
> > been the ability to create a lock file to synchronize log accesses.
> 
> 1.94.3.  But, why would the lock file go into the log directory, that's
> not too smart?

Smart or not, the Mj standard locking paradigm uses lock files in the
same directory as the file being locked and has back to at least 1.93,
so I'm a little confused as to how upgrading to 1.94.4 had anything to
do with this revelation. If you we getting away with having the log file
somewhere else before, you need to do the same magic you were doing
before to allow that.

-- 
 Dave Wolfe


References:
Indexed By Date Previous: Re: The majordomo log file... (1.94.4) two items
From: "Brian L. Heess" <dmbong@commline.com>
Next: Re: The majordomo log file... (1.94.4) two items
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Indexed By Thread Previous: Re: The majordomo log file... (1.94.4) two items
From: "Brian L. Heess" <dmbong@commline.com>
Next: Re: The majordomo log file... (1.94.4) two items
From: tneff@panix.com (Tom Neff)

Google
 
Search Internet Search www.greatcircle.com