UPDATE: peculiar behaviour of ls under 5.0A (fwd)

From: ALLAN HAWDON <allan.hawdon_at_kcl.ac.uk>
Date: Wed, 24 Jan 2001 11:49:20 +0000 (GMT)

Original question:

I've recently upgraded from 4.0D to 5.0A via 4.0F on an
Alphaserver 4000. I now find that for any newly created accounts
the ls -l command show numeric values for UID and GID, instead
of names. This is for any directory the user may list. Accounts
created before then show names for these values as usual. This is
a "standalone" system and we aren't using anything like NIS.
Any suggestions would be gratefully received.

===============================================================

First off, thanks to LHERCAUD, Tom Blinn and Mario Fortier for
their suggestions.

We still have funnies, but I've found that adding the user to
the system group "solves" the problem. This would seem to imply that
it needs access to some file via the g: permission. However all of
/etc/passwd, /etc/passwd.dir /etc/passwd.pag and /etc/group are world
readable. I've run mkpasswd just to make sure everything is up to date.
We aren't using enhanced security and we aren't using ACLs so it's
rather mysterious.

On a different, although related to 5.0A upgrades, note, someone
asked about problems upgrading from 4.0F -> 5.0A (sorry I've deleted
the message). Apart from the above, the only other problem we had was
a bug in the v5.7 firmware which ships with the kit and prevents the
console from seeing the KZPAC raid controller properly. Upgrading to
v5.8 solves the problem. This may only affect 4000s, I'm not sure.

Allan Hawdon
Computing Centre
King's College London
 
Received on Wed Jan 24 2001 - 11:51:13 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT