HP-UX

Hello, I'm quite new to HP-UX and I stumbeled upon some strange behaviour from tar.

I have a script like this:
find -mtime $days -type f|xargs tar cvf tarfile.tar

and it make me a tar file with files that has been changed in $days.
When i run 'tar tf tarfile.tar' it give me output like this:
File1
dir1/dir2/File2
dir1/dir2/File3
...

But when i try 'tar xf tarfile.tar' I get:
tar: File1 - cannot create
tar: dir1/dir2/File2 - cannot create
tar: dir1/dir2/File3 - cannot create
...

I have tried this with GNU tar on same machine, and then it work (same user, same file and destination). The same on Solaris. I'm not sure what version of tar this is but the HP-UX is 11i version 1.

I hope someone can help me with this one

best regards.

there is nothing special in hp-ux tar. this message will come if file/directory creat permission is not there.

Different versions of tar handle a tarball taken from the root filesystem (/) differently. One will restore to the current working directory, an other will restore back to / (and would produce the error you see).

Could that be happening here?

Edit: It's also unusual to call find with no directory to serach over. I'd suggest putting a '.' between find and -mtime...

Thank you for your answers and time

Smiling dragon: sorry, that was just a typo. I have a var stating the directory find shall search through.

And regarding file perms in the mentioned directories, they are ok. I'm able to use gnu tar with same file, same user and same directory.

But to whereas hp-ux tar have some issues with directories, I have tried various approaches.

1. in the example in my original post I've stripped away leading ./ that "find ..|xargs ..." made in the tarball. This does not work.

2. I've tried with leading ./ in tarball, does not work.

3. Absolute paths is out of question, but work :/

I'll be looking into this some more, and I hope we'll find a solution for this. (Other than using GNU tar )

Best regards.

Well, I notice that the man page says to use the o function modifier key when this happens. Maybe you should try that.

I saw that too, but I could not get tar to behave any better.