https://bugzilla.novell.com/show_bug.cgi?id=396842
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=396842#c2
Jon Nelson changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|jnelson-suse@jamponi.net |
--- Comment #2 from Jon Nelson 2008-06-05 13:37:30 MDT ---
Apparently, GNU tar waits until the ENTIRE ARCHIVE has been extracted
(successfully or not) to go back and change some 0-byte files to symlinks.
I was able to observe this by creating a 20MB archive, and killing the
extraction before it was complete. Then, I tried it again and allowed it to
complete. The first time, 0-byte files were created. The second time, the
appropriate symlinks were in place. I straced things and you can see this:
open("./bin/pidof", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0) = 6
..
and then later, *after* the archive has been read in its entirety...
lstat64("./bin/pidof", {st_mode=S_IFREG, st_size=0, ...}) = 0
unlink("./bin/pidof") = 0
symlink("/sbin/killall5", "./bin/pidof") = 0
lchown32("./bin/pidof", 0, 0) = 0
WHY GNU tar behaves like this when other tars (pax, star, etc...) do not is
beyond me but it's hugely frustrating behavior. It's not strictly a bug but IMO
it's pretty ugly.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.