[prev in list] [next in list] [prev in thread] [next in thread] 

List:       majordomo-users
Subject:    Re: Digests and Archiving
From:       Rob Day <rday () tsl ! state ! tx ! us>
Date:       2001-12-28 17:55:30
[Download RAW message or body]

Thanks for your help, Ed. I made the change you suggested (i.e. digest_issue
= 1) and the first digest was named v01.n001. However, after posting to the
list and forcing a digest it still failed to increment. I noticed in the
past that it would encounter errors while creating a digest. I'm guessing
that it wanted to create the file robtest_digest.config.out, but it already
existed and it was unable to modify it. Here's the error message:
	mj_digest: WARNING
	Failed to open temp file
	'/home/lists/majordomo/lists/robtest_digest.config.out', it exists
	mj_digest: ABORT
	Can't create new config file
	/home/lists/majordomo/lists/robtest_digest.config.out
I figured that this temp file was necessary to allow the digest to
increment. So I deleted the robtest_digest.config.out in the hopes that
mj_digest would then be able to do what it needed to do. Still no dice. It
didn't create robtest_digest.config.out and the digest didn't increment.
That makes me feel like it's a permissions issue, but I don't really know
what to do about it. Thanks again.
-Rob

-----Original Message-----
From: Ed Kasky [mailto:ed@esson.net]
Sent: Friday, December 28, 2001 11:18 AM
To: Rob Day
Subject: Re: Digests and Archiving


Robert -

Does robtest_digest.config contain the following:

         # digest_issue         [integer] (1) <digest>
         # The issue number of the next issue
digest_issue        =   <nn>

You replace <nn> with 1 for the first one and then it will continue on 
until you change it yourself....

Ed

At 10:41 AM Friday, 12/28/2001, you wrote -=>
>First of all, please excuse my ignorance. I have indeed looked through
>existed documentation but I still need help. I would like to archive some
of
>my lists automatically. Having read that digested lists are archived
>automatically, I created a digest of one of my lists. This only seemed to
>sort of work. An archive will be created but it will be overwritten by the
>next archive that's created. That is, if the list is being digested daily,
>today's digest will overwrite yesterday's thereby leaving me without an
>archive. The name of the digest doesn't increment. It only creates
v00.n000.
>This is the message I get back from majordomo whenever I force a digest:
>--
>
> >>>> mkdigest robtest_digest ******
>producing This is a Digest of the robtest list V #
>         processing /home/lists/majordomo/lists/digest/robtest_digest/001
>         processing /home/lists/majordomo/lists/digest/robtest_digest/002
>mj_digest: WARNING
>Failed to open temp file
>'/home/lists/majordomo/lists/robtest_digest.config.out', it exists
>mj_digest: ABORT
>Can't create new config file
>/home/lists/majordomo/lists/robtest_digest.config.out
>
>
>This looks to me like the permissions are set wrong but when I take a look
>everything seems ok to me:
>-rw-rw-rw-   1 majordom daemon        468 Dec 19 12:16
robtest_digest.config
>-rw-rw-rw-   1 majordom daemon      13729 Nov 12 12:40
>robtest_digest.config.out
>
>Ideally, I would be able to archive the lists without having to create a
>digest, but I'm not really sure how to get archive2.pl to work. After I
>create an entry for it in my /etc/aliases files, I don't know what to do.
>Any suggestions? Thanks.
>
>________________________________________________
>Rob Day
>Texas State Library and Archives Commission
>rday@tsl.state.tx.us

Ed Kasky
Los Angeles, CA
. . . . . . . .
I put instant coffee in my microwave and almost went back in time.

[prev in list] [next in list] [prev in thread] [next in thread]