At 11:02 AM 10/6/00 -0400, Charlie Summers wrote:
I have a list that often will go a day or so without any posts, which unhinges the next 2pm digest delivery.
Er...if you have nothing to send, why would you want to send it in the first place?
Because what happens is that after a day or two has passed without any list activity, one or more people will post in the morning, but the digest is not delivered on schedule in the afternoon. I have the digest age set to 24 hours, so the digest is initiated with a post, but not liberated until the following day. Yes, of course we do not require a digest when there has been no activity ;-) Sometimes this list is quite active, but will also go dormant for a day or so at a time. The digest subscribers want a daily digest in the afternoon, so they don't miss out on anything from earlier in the day. I've experimented with a variety of settings trying to find the right combination to generate at least one digest a day when there is activity. Your suggestions are welcome and appreciated!
2) Check to see if you have anything in there to send by checking for the existance of archive/digest.body (man test will help here)
I'm not sure that this one is necessary because I believe that flush_digests does this test and exits early if there is no digest.body (I don't have access to the flush_digest code right now, but I noticed this somewhere)
3) touch .digest.force
4) ../.bin/cronlist
Thanks! This is helpful, and I will man touch to find out more. I know that a better knowlege of unix would help, and I'm working on that! linda