David Bear wrote: > On Wed, Apr 25, 2007 at 10:59:19AM -0400, Rodney M. Dyer wrote: >> At 08:57 AM 4/25/2007, Stephen Joyce wrote: >>> Hi David, >>> >>> Are you accessing the AFS folders via a UNC path (\\afs\...) or a mapped >>> drive (H:..., etc)? >>> >>> I saw this issue only when trying to use a UNC path, as advised by the >>> docs. When I went back to mapped drives, refreshes are always immediate. I >>> reported this bug: >>> http://grand.central.org/rt/Ticket/Display.html?id=50864 There's a bit >>> more technical info in RT from Jeff Altman on this problem. >> Ah that's it, Stephen is correct. I remember now that I had the same >> problem a few of years back when I was experimenting with changing the user >> profile and redirected folder paths to use UNC paths instead of drives. > > then we know the issue has been around for a long time. Do we know > that it is really a bug with openafs code or is it with the smb server > code (or microsoft).. > > It sure would be great if a couple of large users could put of the > money to make openafs into an installable file system... > >> I certainly wish this was fixed, however I "assumed" at the time that this >> was an issue with Microsoft, and that UNC paths work that way "by >> design". This problem is preventing me from migrating away from drives >> where I can. >> >> Rodney
The UNC path notification bug is listed as a known issue on http://www.openafs.org/windows.html There is an open issue with Microsoft on this one. I can't fix it without their help. The AFS client service is sending the notification. The CIFS client is dropping it on the floor. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
