Great Circle Associates Majordomo-Users
(December 1996)
 

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

Subject: Re: Locking a locked file..?
From: Dave Wolfe <dwolfe @ risc . sps . mot . com>
Date: Wed, 4 Dec 1996 13:48:17 -0600 (CST)
To: uunet!navi . net!jdawson @ uunet . uu . net (Jim Dawson)
Cc: uunet!GreatCircle . COM!majordomo-users @ uunet . uu . net
In-reply-to: <Pine.BSD/.3.91.961204104627.4987J-100000@dnacom.com> from "Jim Dawson" at Dec 4, 96 11:02:38 am
Reply-to: Dave Wolfe <david_wolfe @ risc . sps . mot . com>

[ Jim Dawson writes: ]
> 
> I installed 1.94 [...]
> 
> However, I got two identical messages from majordomo each on two different
> days:
> 
> WARNING ()
> shlock: open("/usr/local/majordomo/L.Log"): No such file or directory
[...]
> As best I can tell, MD locks the Log file, making it L.Log, and then tries
> to lock it again....? 

Actually it's a race condition when multiple processes are trying to
lock the same file. The line producing the warning should probably be
qualified by "if $shlock_debug" since it looks to me like it detects a
perfectly normal condition (another process released its lock between
the time this process detected the lock and when it tried to see if the
lock was valid). Don't worry about the messages.

-- 
 Dave Wolfe


References:
Indexed By Date Previous: Re: Reply-To
From: Ron Emaus <remaus@great-lakes.net>
Next: Re: archive.pl and wrapper problem
From: Ron Emaus <remaus@great-lakes.net>
Indexed By Thread Previous: Locking a locked file..?
From: Jim Dawson <jdawson@navi.net>
Next: screwed up permissions/ownership/something...
From: David Schlussel <dschluss@sbexpos.com>

Google
 
Search Internet Search www.greatcircle.com