[ Bonnie Scott writes: ]
>
> Suddenly, at digest #551, one of our lists stopped digesting properly.
>
> 1) Articles accumulate in proper directory
> 2) Digest get sent out with all articles in directory
> 3) * Directory does NOT get cleared out
[...]
> We _may_ have done something that messed up the permissions on the subscriber
> files... can't see how that would affect digesting, though, and I fixed it
> anyway.
More likely that the permissions/owners of the directory where articles
accumulate is wrong. Doesn't make sense though that it's able to create
files there but can't unlink them. If it's getting them into the
digests, then the file globbing must be working too.
> 2) digest-config set at
> # maxlength [integer] (40000) <resend,digest>
> # The maximum size of an unapproved message in characters. When used
> # with digest, a new digest will be automatically generated if the
> # size of the digest exceeds this number of characters.
> maxlength = 58000
Is the 'digest_issue' getting incremented? If not, then it sounds like
digest is unable to do the writeconfig after it increments it. If it
aborts in writeconfig, then the unlink never gets done because digest
never gets a chance to finish. In that case it would appear to be a
list-digest.config permissions/owners problem (or the parent directory).
--
Dave Wolfe
References:
|
|
