It seems that this oddity appears when you have 'nobody' or some other user (nfsnobody) assigned to uid '-1' in a 64 bit linux nobody uid 99 nfsnobody uid 65534 -- Manuel Moreno manolo at miconexion.com