(*** This bug was imported into bugs.kde.org ***) Package: korn Version: 0.2 (using KDE 2.2.2 ) Severity: normal Installed from: SuSE Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.4.7-4GB OS/Compiler notes: Dear Korn-responsible person. I'm having trouble with korn after a recent upgrade from SuSE linux 7.2 to SuSE linux 7.3. Specifically: if I use a local mbox file (/var/spool/mail/gorm) then korn works OK but if I use korn to check for mail in an mbox file on another machine (see below for details) then korn does not update its mail count upon arrival of new mail (even though this worked before the upgrade). The gory details: my linux box is in a local network with a bunch of SGI (Silicon graphics) machines. Using "autofs" my linux box mounts certain parts of the file systems on those machines. Among other things the /var/mail/gorm directory on one of the SGI machines is mounted on my machine under the name /home/.nfs/mail/gorm. This means that /home/.nfs/mail/gorm on my machine is in reality the mbox file /var/mail/gorm on the SGI. Hope things are clear so far...;-) For administration purposes my mail arrives on the SGI machine in the directory /var/mail/gorm. In order to access that file I've simply (!) made /var/spool/mail/gorm on my linux machine into a symbolic link to /home/.nfs/mail/gorm on my machine which is in fact a mount of the SGI-file /var/mail/gorm. That way mail can arrive on the SGI machine and I can read it on my own machine. BUT for some reason korn is unable to discover when new mails arrive when I use this setup. Strangely this worked fine before the upgrade from suse 7.2 to suse 7.3. Furthermore if I remove the symbolic link (meaning that now /var/spool/mail/gorm is a local file) and then try sending mail to my own machine THEN korn works just fine. So it seems that something goes wrong when korn tries to access the remote mounted file. Is this a bug? Am I making myself even remotely clear? I've greatly enjoyed korn so far so any help would be appreciated! Best regards Anders (Submitted via bugs.kde.org) (Called from KBugReport dialog)
Thanks for the report. This seems to be caused by the symbolic link. KOrn checks the file after a specified period of time. But it only checks if the file is change by the time of the file. The time of the symbolic link doesn't change, so KOrn thinks there is no new email. This should be solved with KDE 3.4. Then, the check for the file time is omitted.
Is this bug still present in a recent version of KDE, such as 3.5.8 or KDE 4 RC2?
Closing due to no response from reporter. Please reopen if this bug still exists in KDE 3.5.8 or 4.0.0.