If anyone questions the version of 1.94. It says that because I
changed it in the source. This is MJ 1.94.1 running on BSDI 2.1 with *no*
NFS.
In case you need more info here is a piece of /tmp/majordomo.debug. There
are lots of entries like this:
mj_majordomo: WARNING
shlock failed: write('/usr/local/majordomo-1.94/shlock.21193', '21193'):
Bad file des
criptor
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440.
mj_majordomo: WARNING
shlock: open('/usr/local/mail/lists/list.config.LOCK'): No such file
or directory
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
Can't fork at /usr/local/majordomo-1.94/majordomo.pl line 440, <STDIN>
chunk 1.
mj_majordomo: WARNING
shlock: open('/usr/local/mail/lists/list.config.LOCK'): No such file
or directory
mj_majordomo: WARNING
shlock: open('/usr/local/mail/lists/L.list'): No such file or
directory
On 7 Feb 1997, Jason L Tibbitts III wrote:
> >>>>> "TG" == Tom Glover <tomg@boiled.egg.com> writes:
>
> TG> I'm not so sure that its plugged. One of my larger lists got its
> TG> subscriber list zeroed last week following some race conditions.
>
> Could you describe these race conditions? When testing 1.94.1 before its
> release, I ran it through the torturous task of processing 10000
> simultaneous subscriptions _and_ 10000 simultaneous unsubscriptions on a
> list that already had 20000 members. This drove load averages through the
> roof (100+) and took a really long time to get through everything but at
> the end the list was essentially as expected. There were a few lock
> timeouts and such but the list was not zeroed.
>
> Of course that's not a scientific test and it only proves that the locking
> for subscriptions and unsubscriptions is at least pretty good on my
> platform. If there really is a locking bug I'd really like to find the
> root of it.
>
> - J<
>
--
Regards,
Tom
________________________________________________________________________
| "The Egg Domain" | "And all you touch and all you see, |
| tomg@egg.com | is all your life will ever be." |
| http://www.egg.com/ | (Pink Floyd) |
|
|
