If I recall correctly, .../latest/java is a soft link to the actual
version of java. It is the permissions on the real directories that
matter, I believe.

Richard Gambrell
Database Administrator


On Sat, 19 Sep 1998, Alan AMBERS wrote:

> Jeff -
>
> Here is the output from ls -ld for the permissions:
>
> shell/iX> ls -ld /usr
> drwxrwxr-x  11 MANAGER.SYS       0           1184 Sep 19 15:27 /usr
> shell/iX> ls -ld /usr/local
> drwxrwxr-x   3 MANAGER.SYS       0            512 Sep 19 15:27 /usr/local
> shell/iX> ls -ld /usr/local/java
> drwxrwxr-x   3 MANAGER.SYS       0            512 Sep 19 15:27 /usr/local/java
> shell/iX> ls -ld /usr/local/java/latest
> lrwxrwxrwx   1 MANAGER.SYS       0              8 Sep 19 15:27 /usr/local/java/l
> atest -> jdk1.1.5
> shell/iX> ls- -ld /usr/local/java/latest/bin/PA-RISC
> drwxr-xr-x   3 MANAGER.SYS       0            416 Sep 19 15:28 /usr/local/java/l
> atest/bin/PA-RISC
> shell/iX> ls -ld /usr/local/java/latest/bin/PA-RISC/green_threads
> drwxrwxr-x   2 MANAGER.SYS       0           2624 Sep 19 15:28 /usr/local/java/l
> atest/bin/PA-RISC/green_threads
> shell/iX>
>
> Everything looks ok to me.
>
> I also found a response in dejanews from my first message I sent
> a week ago from Mike Yawn, The Exalted Grand Poobah
> of Java/iX.  The message didn't make it back to hp3000-l
> (newsgroup problems from last week I guess.)
>
> I tried his suggestion, but also came up with the same problem.
> Here is his message (response to my original from September 13):
>
> >| File permissions have really been the bane of my existence since
> >| I started doing Java.  I haven't been able to succeed, even using
> >| the specific tar options that are supposed to preserve permissions,
> >| it getting things to come out of the tarball with the same
> >| permissions they went in with.
> >|
> >| In 6.0, the Java install job specifically goes back and re-sets
> >| the permissions after untarring the files; it appears I need to
> >| add an install script to the FREEWARE tape and the download on
> >| Jazz to accomplish the same thing.
> >|
> >| From the output you included, it looks like you have everything
> >| set properly on the Java program file.  However, the Java program
> >| file has an XL list, and some of the XLs also have dependent
> >| libraries; so failure to reach any of these libraries will also
> >| result in the failure you've seen.  You can continue tracking
> >| down each file as you've done so far, or basically take a
> >| sledgehammer to the whole mess by doing:
> >|
> >| shell/iX> chmod 755 /lib/lib*.sl        ( to get libc, libm, libsvipc )
>
> >| shell/iX> chmod 755 /usr/lib/lib*.sl    ( go get libsocket )
> >| shell/iX> chmod -Rf 755 /usr/local/java/latest  ( to get all of Java )
> >|
> >|
> >| Mike
>
>
> From what Mike suggests, it must be a dependent library.  What other
> libraries can I look at and use the sledgehammer to fix?
>
> /alan
> [log in to unmask]
>
>
>
> Jeff Kell on hp3000-l said....
>
> >Get in the shell and traverse this one directory at a time:
> >
> >shell/iX> ls -ld /usr
> >shell/iX> ls -ld /usr/local
> >shell/iX> ls -ld /usr/local/java
> >   ...etc...
> >
> >Check the permissions on the directories.  Out of the possible
> >
> >   drwxrwxrwx
> >          ^ ^ you need at least read/execute for 'other' on each level.
> >
> >If you cannot 'traverse the directory' as the error above indicates
> >then you are missing that trailing 'x' somewhere down the line.  This
> >'x' allows you to see the files in the directory, while 'r' allows you
> >to read the files in the directory.  But since you have an absolute
> >pathname already, you are probably missing r/x both.
> >
> >Jeff Kell <[log in to unmask]>
>