Path name element too long - skipped

[George Barbitsas]

i started a same thread in sysadmin but anyways no biggie

I am running

HP-UX hsapp24 B.11.11 U 9000/800 2327653465 unlimited-user license

Ignite-UX-11-11 B.5.3.35

these are the erros im geting from pax

pax: usr/sap/PP1/J93/j2ee/cluster/server0/temp/webdynpro/public/sap.com/tc~wd~corecom
p/ComponentInterfaces/com.sap.tc.webdynpro.components.interfaces.Confirmation
DialogInterface/ConfirmationDialogInterface.xml : Path name element too long - skipped


anybody know what i need to do in order to make this go away? patching pax maybe?

ThX

[Steven E. Protter]

Shalom Eric

http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHCO_32438&context=hpux:800:11:11

That is the pax patch.

The version of Ignite you are using is unstable and should be upgraded.

There are however some things that can not be fixed. That is a very, very long string and maybe you want to do something to shorten it.

Still there are other options to try first.

SEP

[George Barbitsas]

yeah i know but unfortunatly i have many more were that came from...does the patch pax fix this?

[Bill Hassell]

Neither the he pax patch nor the pax man page mention (or extend) the pathname limit. Since pax is based on the POSIX.2 spec, the constant: _POSIX_PATH_MAX may come into play. Use the pathchk command to verify:

pathchk /usr/sap/PP1/J93/j2ee/cluster/server0/temp/webdynpro/public/sap.com/tc~wd~corecom
p/ComponentInterfaces/com.sap.tc.webdynpro.components.interfaces.Confirmation
DialogInterface/

It is certainly possible that an extremely long pathname works fine in the filesystem and shells, but certain provgrams and utilities cannot handle massively long name. I would suggest moving /usr/sap to another volume group to solve this (and other potential) problem(s).