Great Circle Associates Majordomo-Workers
(December 1997)
 

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

Subject: Re: Abort message ambiguous?
From: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Date: 02 Dec 1997 13:10:01 -0600
To: majordomo-workers @ greatcircle . com
In-reply-to: Brock Rozen's message of Tue, 2 Dec 1997 16:21:14 +0200 (IST)
References: <Pine.OSF.3.96.971202162005.5645A-100000@webdreams.com>

>>>>> "BR" == Brock Rozen <brozen@torah.org> writes:

BR> What causes these errors?

There's only one place in the source where it occurs:

            # Either the request is approved, or the list is open and the
            #    subscriber is the requester, so check to see if they're
            #    already on the list, and if not, add them to the list.
            # Lock and open the list first, even though &is_list_member()
            #    will reopen it read-only, to prevent a race condition
            &lopen(LIST, ">>", "$listdir/$clean_list")
                || &abort("Can't append to $listdir/$clean_list: $!");

BR> The message itself is ambiguous. Don't you append *because* the file
BR> exists?

Blame your OS; the "File exists" part comes from it, not Majordomo.  Mj's
just noting the failure to append to the file (eith error code 17, EEXIST)
and returns the OS error string.

I don't know why that particular error would come about; perhaps lopen is
failing in some other weird way which causes the error.  Dave, you're the
locking expert; do you have any idea?

 - J<


Follow-Ups:
References:
Indexed By Date Previous: Abort message ambiguous?
From: Brock Rozen <brozen@torah.org>
Next: Re: Abort message ambiguous?
From: Dave Wolfe <dwolfe@risc.sps.mot.com>
Indexed By Thread Previous: Abort message ambiguous?
From: Brock Rozen <brozen@torah.org>
Next: Re: Abort message ambiguous?
From: Dave Wolfe <dwolfe@risc.sps.mot.com>

Google
 
Search Internet Search www.greatcircle.com