At 11:39 AM -0400 6/11/01, Admin Mailing Lists wrote:
> so then even if you use server mode with fast-update, you have to put the
> pop temp directory on the same partition? just confirming, as i couldn't
> find this note in the Documentation Manual. I'm assuming it's because you
> can't do renames/moves across filesystems?
Correct.
>
> lastly, can someone explain in detail the use of --disable-old-spool-loc?
> I know what the manual says, but I still don't quite understand what is
> considered "old".
> It SEEMS that it means a .pop file from a previous session. So if you
> enabled --disable-old-spool-loc, it wouldn't generate pop lock busy errors
> if a .pop file existed for the user? (since it's not checking for them?)
This option tells Qpopper not to check for old .user.pop files in the
spool directory. It only has meaning if the temp directory has been
changed to be something different from the spool directory or if
hash-spool is set. When that's the case, normally (just to be safe),
Qpopper checks for old .user.pop files in both the "old" location
(the spool directory) and the "new" location. If you know there
aren't any leftover old spool files in the spool directory, you can
turn off the extra check.
