FYI.... I've posted a patch file which contains the major spoolss fixes in the SAMBA_2_2 cvs tree. These include * security descriptor parsing fix for Win2k clients * correct access checks for modofying forms using a print server handle * add check for 0 length printer data in EnumPrinterDataEx() * fix alignment/offset bug in EnumPrinterDataEx() * fix bug in DeletPrinterDriver() so that it deletes the correct architecture You can grab the patch set from http://download.samba.org/samba/ftp/patches/jerry/post-2.2.5 Look for "samba-2.2.5-printing.patch". Of course, you can also just grab the latest SAMBA_2_2 cvs tree. Thanks to everyone for the feedback so far. cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Dear all, If I mount a remote linux partition using smbmount and write one file to that partition. How could I make sure that that file is really written to the remote disk successfully? I know that some cache mechanisms existed in linux kernel. So I guess there may be two possibilities as below: 1. After the call write() returns successfully, the file has been actually in the local cache and then submit to remote cache later. 2. After the call write() returns successfully, the file has been actually in the remote cache and then submit to remote disk later. Then, no matter which one of the above two situations happens, the data is not yet written to the physical storage at that time, right? Should I need to call fsync() each time after calling write()? Thanks a lot! Regards, Kevin