Re: Digesting problem

Howard,

This line (or similar) occurs in digest, resend, majordomo, and config_parse.pl
so I would NOT add closing a apostrophe.  I am sure if you check the old server
you will find the same syntax, yet everything was working.

Have you verified your maxsize/maxlines etc. in the config file for your digest?

Without "fixing what isn't broken", are you seeing expected results now?

Dan Liston

Howard R. Hamilton wrote:
> Greetings!
> 
> Thank you for the quick reply.
> 
> I am running running Majordomo 1.94.5.  The server is up to date on all apps
> till September 2008 (last major upgrade of all systems then).  When I moved
> the list to the new server, I copied the configuration scripts for the lists
> exactly, but did a new install of the majordomo software and ran it on a test
> list for a couple days first.  The wrapper file was recompiled during the
> installation.  I created a new UID/GID for majordomo as per the install
> instructions and set UID/GID to this for all of the majordomo components
> before do the make / make install.
> 
> I have only dabbled in Perl a bit, but when I implemented the change suggested
> below, emacs' syntax highlighting indicated an unclosed single apostrophe in
> the previous function that might also be a problem.  The offending line looks
> like this:
> 
>             &config'writeconfig($listdir, $opt_l);
> 
> Is that correct syntax for Perl, or should I close that single apostrophe at
> the end of that line.  It is the last line in that function.
> 
> Thanks again.
> 
> BUZ
> 
>> Hello Howard,
>>
>> What version of majordomo are you running?  I imagine your new server is also
>> using new versions of perl, sendmail, etc.  Did you maintain the same UID/GID
>> for the majordomo user, and all/any of it's files, directories, and workspace
>> when you migrated to the new machine?  Did you keep the original scripts and
>> config files or did you install new?  I would assume the wrapper had to be
>> recompiled to be compatible with the new OS.  The numeric uid/gid would come
>> into play here too.
>>
>> Lastly, I do not know the root cause, but there is a simple cure for at least
>> part of your digest problems if you are running version 1.94.5 of majordomo's
>> digest script.  In diff format;
>>
>> 176c176
>> -     foreach (@files) {
>> ---
>> +     foreach (sort @files) {
>>
>> This translated into english means
>> change line 176 of the digest file from the matching line starting with a -
>> to look like the line starting with the +.  The plus and minus only indicate
>> what comes out and what goes back in.  They are not part of the line itself.
>>
>> If you are running some other version of majordomo, you may find a similar
>> solution, but the line numbers might not match.
>>
>> On new sendmail versions owner/group/other permissions must be set correctly
>> for everything to work properly too.
>>
>> Dan Liston
>>
>> Howard R. Hamilton wrote:
>>> Greetings!
>>>
>>> I have been running a mailing list with majordomo since 2002 (it actually
>>> started in 1994 but I was only a subscriber and contributor before that).
>>> The
>>> list was actually composed of a moderated list, an un-moderated list and a
>>> digest of the moderated list.  Everything was working fine until I had to
>>> move
>>> it to a different server (old server was being retired, and the domain was
>>> retiring with it.)
>>>
>>> The old system was on BSD linux, and the new system is on Oracle (Red Hat
>>> derived) linux.  Since the move, the system has not been able to create
>>> digests properly.  There are two main symptoms, the size of the digests (set
>>> at 28k, and varies from 2k to 15-20k) and the ordering of the email messages
>>> (they seem to be put out in a semi-random order).
>>>
>>> The size problem can be very irritating, because it will start putting out a
>>> digest with every new message that occurs.  Since I am away from a computer
>>> for several days at a time, and the list gets 10-30 emails a day, there can
>>> be
>>> a lot of single email digests of 2-4K in size.
>>>
>>> When this problem occurs, I will find numerous emails in the digest storage
>>> area of varying age, and will notice that most of those emails stay around
>>> for
>>> several digest creations.  If I trigger digest creation two or three times
>>> ("echo mkdigest list passwd | mail majordomo") it will clean out all of the
>>> emails in the storage area and then start "sort-of" working (all emails go
>>> out, but digest size still varies from 5-15k) for a few days.
>>> Unfortunately,
>>> those digests never get mailed out, even though they were created and are
>>> available from the archive.
>>>
>>> Has anyone else ever experienced a problem like this, and how did you solve
>>> it?
>>>
>>> BUZ
>>>
> 
>