On Saturday, Oct 19, 2002, at 00:25 US/Pacific, Randall Gellens wrote:
Is there any way to disable caching for everyone, without having to re-configure and re-compile? Especially, is there a command line option? We get enough pop processes on our server that having config files creates a resource contention problem on the disk where the config file lives, so config files == bad.At 12:50 PM -0700 10/1/02, John Rudd wrote:Since upgrading some of our daemon's from qpopper 3.1 to qpopper 4.0.4,You could disable caching for those users, which would turn off the log messages (since Qpopper wouldn't attempt to create a cache file).
I've noticed some errors in our pop logs:
Oct 1 00:10:00 cats-po-1.ucsc.edu /usr/local/lib/kpopper[1011]: [ID
702911 local1.notice] Can't write cache file for XXXXX; spool is in mmdf
format
(where XXXXX was the account name)
We didn't used to get this, and we're now getting it a LOT (ie. taking
up lots of disk space with the log messages).
And that brings me a to another question ... can you make more of your config file options available on the command line? For example, there appears to be no default location for the ssl cert AND there appears to be no way to set it on the command line (according to the pdf file). (not that I really want there to be a default location, since it would probably be somewhere hanging off of the root disk, and that just leads back to the resource contention issue ... as opposed to the cert file itself which I can put on a disk that wont be used for much else, reducing IO contention)
Ideally, every config file option would have a CLI equivalent.
