Date: Tue, 8 Dec 1998 12:46:40 -0800 (PST) From: Mike Harshbarger <mharsh@fsr.net> To: freebsd-isp@FreeBSD.ORG Subject: Leftover qpopper drop files Message-ID: <Pine.BSF.3.96.981208120652.9822E-100000@archer.fsr.net>
next in thread | raw e-mail | index | archive | help
I've recently moved my mail server from a Solaris x86 platform over to FreeBSD. I *love* the performance improvement, but I've run into an irritating qpopper problem. As a friend put it: "Oh, you've got the new qpopperdropper!" :) I've ran qpopper 2.53 on both systems. Qpopper creates a temporary drop file named /var/mail/.username.pop. On Solaris, this file was deleted after use. They hang around in FreeBSD. If a new customer happens to pick the same username as a old, deleted account, they'll get this error when they try to pop their mail: -ERR System error, can't open temporary file, do you own it? And then I get to jump in and either delete or chown the leftover temporary drop file. I'm wondering if anyone else has seen this problem, or if I've caused it with a compile-time option or an ignorant filesystem choice. Right now, /var/mail is a symlink pointing at a directory in a ccd array mounted with the 'noatime' option. (noatime is a holdover when I was experimenting with inn on this ccd, and I'm thinking I should get rid of it) It'd be easy for me to cron a script that would chown the temporary files to the correct userid or simply delete ancient ones, but I don't want to if I can fix this problem another way. Thanks in advance, ___ ___ ___ | __/ __|_ _| Mike Harshbarger, First Step Internet | _|\__ \| | System & Network Administrator |_| |___/___| (208) 882-8869 / 1-888-676-6377 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981208120652.9822E-100000>