When we look at /opt/x/x.jar, the permissions are fine. Now comes the strange part.
After some tries we ended up with (d.jar was obsolete):
a.jar -> /opt/a/a.jar
b.jar -> /opt/b/b.jar
c.jar -> /opt/c/c.jar
x.jar -> /opt/x/x.jar
and everything works as expected.
Then we:
1. remove the symlink x.jar
2. add a new (dummy) file to this directory
3. make the symlink again
4. remove the dummy file
Now the problem occurs again and we get the above io.FilePermission exception.
Now if we:
1. remove the symlink
2. make the symlink again
The exception is gone, it seems as if the symlinks takes the physical place of the dummy file on the filesystem.
Redoing the above sequences gives again the FilePermission exception and finally OK again.
Some background info, the OS is Solaris 10 (sparc) using UFS filesystem. JDK used is 1.5.0_06 but have tested it using 1.6.0_18 with same results.
Sander Hamel wrote:Actually I do believe that this issue is Java releated as the OS has no problem with these files whatsoever.
I wasn't disagreeing with you. I just moved your question out of our IO forum, which deals with the Java IO classes, to our Unix forum, which deals with OS-specific issues.
This message was edited 1 time. Last update was at by Joe Ess
Sander Hamel
Greenhorn
Joined: Feb 26, 2010
Posts: 3
posted
0
Joe Ess wrote:
Sander Hamel wrote:Actually I do believe that this issue is Java releated as the OS has no problem with these files whatsoever.
I wasn't disagreeing with you. I just moved your question out of our IO forum, which deals with the Java IO classes, to our Unix forum, which deals with OS-specific issues.
Ok sorry for misunderstanding, I'm still new here :-).