tar problems - tar:couldn't get uname for uid 5200 - problems installing emacs 19.20

tar problems - tar:couldn't get uname for uid 5200 - problems installing emacs 19.20

Post by Edward Hartne » Sun, 14 Nov 1993 00:43:20



I installed emacs 19.20 and at one point during the make install
process got TONS of the following type messages:

Copying /usr/local/src/emacs-19.20/etc...
tar: couldn't get uname for uid 5200
tar: couldn't get uname for uid 5200
x ./COPYING, 17976 bytes, 36 tape blocks
tar: couldn't get uname for uid 5919

What do these mean?

Looking in the directory /usr/local/src/emacs-19.20/etc I see that all
the files apparently made it there OK. Should I worry about this?

Any help of suggestions will be appreciated. Thanks.

 
 
 

tar problems - tar:couldn't get uname for uid 5200 - problems installing emacs 19.20

Post by Joost Helbe » Sun, 14 Nov 1993 02:09:56


   I installed emacs 19.20 and at one point during the make install
   process got TONS of the following type messages:

   Copying /usr/local/src/emacs-19.20/etc...
   tar: couldn't get uname for uid 5200
   tar: couldn't get uname for uid 5200
   x ./COPYING, 17976 bytes, 36 tape blocks
   tar: couldn't get uname for uid 5919

   What do these mean?

   Looking in the directory /usr/local/src/emacs-19.20/etc I see that all
   the files apparently made it there OK. Should I worry about this?

   Any help of suggestions will be appreciated. Thanks.
The tar format has the UID stored per file. Not the user-names.
Tar uses this UID to create the files it extracts, the files end up being
owned by the UID that was in the archive.

When a particular UID doesn't exist on your system, tar issues a warning
and continues anyway.

You can avoid this by using the 'o' option. This option will create the
files with YOU as the owner. This has a great advantage: in your case
you may end up with files owned by some other user on the system and
you being able to e.g. read/write these files.

So: No harm done.
--
   Joost Helberg                              Rijnzathe 6


   Oracle Europe BV                           Product Line Development  
   Phone: +31 3406 94211                      Fax:   +31 3406 65609

 
 
 

1. tar error: couldn't get uname for uid

Our overnight backups use tar, and have been working fine for months. Last
night they failed and our log file had the following error from tar:

tar: couldn't get uname for uid 386

This is one I've not seen before. I've checked the uid, and it's a valid
user and their account is not locked - looks fine as far as I can tell. The
tar process is run as root, not uid 386. Re-ran the backup this morning with
no problems. The system is running HP-UX 10.01 and we're using the standard
tar that came with this OS release.

Anyone else seen this error before, or have any suggestions as to what might
cause it?

Thanks,
Fatus
--
Fatus

2. Help : Palm conduit configuration in RH 8.0?

3. getting a tar file off a tape when you've tar cf'ed first

4. AIX 4.3.3 - C for AIX compiler problem

5. Looking for a better 'tar' than 'tar'

6. Linux messed up my computer !

7. tar -xvf mozilla.tar = tar: directory checksum error

8. Development Environment and Libraries Choices

9. Wanted: rcmd host tar x_?_vqf file.tar file1 ... fileN | tar xvf -

10. tar & mt command. Getting Tar:Unexpected EOF

11. tar problem: cannot change ownership to uid 1000

12. Trouble Inatalling (tar: couldn't get gname for gid 110)

13. Restoring system with tar: uid/gid problems.