>> > I just installed the qmail-popbull patches on a qmail 1.03 install and am
>> > getting duplicate messags, one for every time a user checks their email.
> + if (stat(".timestamp", &st) == -1) ts_date = 0;
> + else ts_date = st.st_mtime;
> + fd = open_trunc(".timestamp");
>Now, for some reason or another, it's not actually modifying the date when
>I check my mail via a POP session. I thought maybe it could be because the
>$HOME directories are NFS mounted
That's what I was about to say, attribute caching across NFS.
>so I enabled pop3d on the NFS server and tried it there but I get the same
result.
If you are *sure* that the modification time of .timestamp isn't changing
when you run the pop server (with the popbull patch of course) on the same
system as the .timestamp file system then I'd say it's either an OS bug or a
particularly interesing mount option with BSDI.
I guess it's possible that the semantics of mtime are such that it doesn't
get updated unless something is actually written to the file...
Hmm. According to Solaris, mtime changes when you issue one of:
creat(), mknod(), pipe(), utime(), and write(2).
Does the patch write anything into .timestamp? Should it?
Regards.
