find error: pwd: The file access permissions do not allow... 1

HI,

If it's just a certain filesystem,I would also try to fsck it.
Also,possibly something is corrupted in security files under /etc.
Can try running:

usrck -y ALL
grpck -y ALL
pwdck -y ALL - these will check the security files consistency

mkpasswd -f - this one will rebuild the password indexes

"Long live king Moshiach !"

got some fun messages but nothing pertaining to my issue. still broke, but thanks for the ideas.

IBM Certified -- AIX 4.3 Obfuscation

Hi Yegolev,

I have seen some funny stuff with pwd occure in situations where the permissions of the underlying directory for a filesystem do not allow access.

Unfortunately the only way to check/fix this is to stop all access to the filesystem, get everyone out of it (yourself included) and unmount it. Then examine/change the perms for the mount point directory (instead of the filesystem itself).

The perms should be set to 755.

Note that this mount point directory could be a few directory levels up from where you are trying to execute that find command.

Just an idea .... hope it helps

____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.

dv3zero, ah yes, i forgot about that one. i bet that's it, has all the earmarks. too bad i can't do anything about it!

IBM Certified -- AIX 4.3 Obfuscation

If you cant get an outage window for a umount, you could try doing it on the fly by double mounting the parent filesystem to another location (so exposing the underlying mount point directory).

Something like "mount /usr /mnt" # If /usr is the parent filesystem in question.

Then something like
"cd /mnt/my/problem/mountpoint/directory" and
"chmod 775 . ; cd / ; umount /mnt"

I have not tried this myself, but can see no reason why this (or something like it) should not work.

Be interested to hear back how it goes if you decide to do it.

Best Regards.

____________________
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debuging Mondays code.

i will test this on a different filesystem and get back to you. looks like i am inheriting a bothersome umask (027) when running my filesystem-creation script.

IBM Certified -- AIX 4.3 Obfuscation