WPhyer;579050 Wrote: > You're right, it's not. But it's also not using the OS properly. I > haven't dived into the source code at all but I suspect that it's not > getting directory/file information properly. When getting directory > information SBS is only issuing a "V3 LOOKUP". It never issues a "V3 > GETACL" command.
Oh my. Applications should NOT be making NFS system calls. The behavior of NFS file systems should be totally transparent to the application. Ie, SBS does NOT issue "V3 LOOKUP" NFS calls... it uses the perl stat function which calls the libc stat, which calls the system call... it is the system call that has to figure out how to implement the call on various file system types, including NFS as well as NTFS, FAT, EXT2, XFS, whatever. All this MUST be transparent to the application or you would need "firefox for ext3 home directories" and "firefox for nfs mounted homes". SBS does NOT KNOW OR CARE if your fs is remote or not: it is the OS's job to make that transparent. > > This is probably a response from a junior maintainer who doesn't fully > understand how the OS works when dealing with networks. And doesn't > want to take the time to learn. > > Thank you "junkmael99" for being one of the few to actually be > proactive with this. Michael is a Junior Maintainer? Haha. Hint: use strace, not tcpdump. That would at least show you what calls are being made BEFORE the OS interprets them. If the os interprets them strangely (highly unlikely --- the NFS code in modern OS's is hardly a new untested feature). Even better, look at the code and show where the NFS code is in SBS. -- snarlydwarf ------------------------------------------------------------------------ snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179 View this thread: http://forums.slimdevices.com/showthread.php?t=81742 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
