Great Circle Associates Majordomo-Workers
(November 1996)
 

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

Subject: Re: Question about V1.93, majordomo and config_parse.pl's direct call to shlock rtn.
From: Dave Wolfe <dwolfe @ risc . sps . mot . com>
Date: Mon, 11 Nov 1996 14:22:21 -0600 (CST)
To: zielonko @ ucx . lkg . dec . com (Karol Zielonko 508-486-5632)
Cc: majordomo-workers @ greatcircle . com
In-reply-to: <96111006413102@ucx.lkg.dec.com> from "Karol Zielonko 508-486-5632" at Nov 10, 96 06:41:31 am
Reply-to: Dave Wolfe <david_wolfe @ risc . sps . mot . com>

[ Karol Zielonko 508-486-5632 writes: ]
>
> In the majordomo script (do_newconfig routine) and the config_parse.pl
> code (get_config routine) direct calls to the shlock routine are made.
> In both cases the calls don't check the return status to see if the
> lock was granted so that it can keep trying to get the lock (like
> lopen does). Can anyone tell me why this is?

Because it's a bug? Even if it doesn't retry like lopen, it should check
the return value before operating on the config file. Otherwise, what
was the point of calling shlock?

-- 
 Dave Wolfe


References:
Indexed By Date Previous: Re: registration, license, copyright of majordomo
From: Bill.Houle@SanDiegoCA.NCR.COM (Bill Houle)
Next: PERL5 broke sub main'ParseMailHeader
From: Walt Haas <haas@xmission.com>
Indexed By Thread Previous: Question about V1.93, majordomo and config_parse.pl's direct call to shlock rtn.
From: zielonko@ucx.lkg.dec.com (Karol Zielonko 508-486-5632)
Next: ANNOUNCE: patches for Majordomo 1.94 available
From: Chael Hall <nowhere@chaos.taylored.com>

Google
 
Search Internet Search www.greatcircle.com