But when we try to put any file that has a resource fork in it like. Just installed this server and transferred file from older OS X server just fine. High Sierra 10.13.4 running OS Server 5.6.1. Confirm, that the lock has NOT been released.Ĭan anyone else confirm this behaviour on OS X 10.13.1?Ĭan anyone else confirm that this is NOT behaviour on versions of OS X older than 10.13. User profile for user: cdean43015 cdean43015 User level: Level 1 (9 points) Question: Q: Question: Q: High Sierra and SMBup stripping resource forks. Confirm there is a lock on the file on the fileserver.Ħ: Close the Preview application viewing the pdf file. ![]() Confirm that the lock has been released on the Samba server (smbstatus -locks").ĥ: Open the pdf from the Samba server with the default Preview application. Confirm there is a lock on the Samba server with "smbstatus -locks".Ĥ: Close the application (not Preview) with the PDF file open. Open it with something other than Preview (The default). So, the real problem, is the Finder's lack of response to the user, but locks not getting released, makes the problem much worse.ġ: Disable all preview functionality in the Finder.Ģ: Browse to a PDF on you Samba fileserver.ģ. Often none of the user's data actually gets uploaded to the server (But they think it has been). To the users, it looks like the operation was completed, but it was not. ![]() If there are any locks on files/folders below the top folder, the request can not be completed, and the Finder (OS X) does not inform the user. Some users have a workflow, were they overwrite entire folder structures on the Samba server. This appears to be new behaviour to OS X 10.13.1. ![]() I think I have made sense of it: In OS X 10.13.1 the Preview application & preview functionality in the Finder, does not release locks (DENY_NONE) on files it has previewed from a (Samba) file server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |