Jon Sjöstedt Posted September 4, 2008 Report Share Posted September 4, 2008 Hello all! In order to not jeopardize concurrent access to a file, I have made some tests with the "deny mode" wire to the "open file" vi. It seems to work (I am using lv 7.1.1 on Solaris). I do accesses from different hosts that map the same NFS partitions. Looking at the file properties during execution of the tests, no permissions are altered. Neither can I see that any kind of lock file is created. I have also noticed the the file is only locked for labview. I can access the file perfectly with emacs or cat. My question is therefore: How is this "deny mode" functionality implemented in solaris? I dont want to break it unintentionally. Quote Link to comment
Rolf Kalbermatter Posted September 7, 2008 Report Share Posted September 7, 2008 QUOTE (Jon Sjöstedt @ Sep 3 2008, 03:39 AM) Hello all!In order to not jeopardize concurrent access to a file, I have made some tests with the "deny mode" wire to the "open file" vi. It seems to work (I am using lv 7.1.1 on Solaris). I do accesses from different hosts that map the same NFS partitions. Looking at the file properties during execution of the tests, no permissions are altered. Neither can I see that any kind of lock file is created. I have also noticed the the file is only locked for labview. I can access the file perfectly with emacs or cat. My question is therefore: How is this "deny mode" functionality implemented in solaris? I dont want to break it unintentionally. Not sure about Solaris really and Solaris in many ways is often a bit special. But on Linux it seems to be implemented by range locking the entire file. fcntl(fd, F_SETLK, &lock) Rolf Kalbermatter Quote Link to comment
Jon Sjöstedt Posted September 9, 2008 Author Report Share Posted September 9, 2008 Thanks! Feels good safe enough... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.