[ Bryce Newall writes: ]
>
> I downloaded the following patches, after reading through the README
> and INDEX files:
>
> config_majordomo.1 List.config file locking patch
> config_parse.pl.1 Config corrected (tech note)
> digest.1 Add a backslash to value of $V{'TO'} (required for perl 5)
> digest.2 Supply default value for resend_host if it is unset
> digest.3 List.config file locking [requires config_majordomo.1]
> shlock.pl.1 Locking bug: Majordomo creates files but can't delete them
> shlock.pl.2 Cleans up the unnecessary whining about lock files
>
> When trying to apply the patch from digest.3, patch claimed that it was a
> previously-applied patch
Hmmm... I only got that on digest.1, because it's unnecessary for
1.94.1. (Note to Joe: either label it in the INDEX as for 1.94 only or
remove it, please.)
> Same thing happened with shlock.pl.1 (I applied shlock.pl.2 first,
> thinking it was all I'd need).
Note the note in shlock.pl.2:
Here's a replacement shlock.pl.1 that cleans up the unnecessary
whining about inablility to open or unlink lock files that are there
one moment and gone the next.
Shlock.pl.1 really shouldn't be there. (Note to Joe: deep six it
please.)
> This time, when I run the digest, the results are worse than before. I
> still get a number of those shlock errors, but then it ends with this
> (and I'm quoting one fo the shlock errors as well):
>
> mj_digest: WARNING
> shlock: link('shlock.6619', ''): No such file or directory
> mj_digest: ABORT
> shlock: too many warnings
The abort is courtesy of shlock.pl.* to keep terminal errors from
causing infinite loops and infinite warning messages. I'll have to look
into the first message. Perhaps there's dependency on another patch. But
it looks like something is pretty severely screwed up that no file name
is getting passed to set_lock(). You might try starting with a "virgin"
1.94.1 digest file and apply only digest.2 and digest.3. Something else
you can do is put this line at the front of your majordomo.cf (assuming
you use -C on the digest command line):
$shlock'shlock_debug = 1 if $main'program_name eq 'mj_digest';
Shlock will then dump trace messages onto stderr, which should be mailed
back to you. Or you can put something like this in majordomo.cf to get
them dumped into a file:
if ($main'program_name eq 'mj_digest') {
open(STDERR, ">>/usr/tmp/debug.digest") ||
die "Can't open /usr/tmp/debug.digest: $!";
}
--
Dave Wolfe
Follow-Ups:
References:
|
|
