SUMMARY: Chown problem; SimpleFS and nfs

From: Amy <amy_at_aloha.nascom.nasa.gov>
Date: Fri, 08 Oct 1999 10:53:36 -0400 (EDT)

Only the UIDs that are already defined on the SimpleFS machine will
work for chown from the unix box. All others map to nobody.

Thanks to

Robert Mulley <genius_at_one.net.au>
"Degerness, Mandell ISTA:EX" <Mandell.Degerness_at_gems2.gov.bc.ca>
Wendy Fong <wfong_at_synacom.com>

for their help.

A separate issue is why the SimpleFS box had defined some of the UIDs
- it appeared to have happened automatically for those UIDs. A topic
for another day.


On Thu, 7 Oct 1999, Amy wrote:

>
> I have a SimpleFS machine nfs mounted onto an alpha running tru64 v4.0f.
> A detar onto the nfs mounted directory left all the files from the
> tar file owned by root:nobody. I tried to chown them to user sswowner
> - and the files were chowned to nobody.
> Some usernames work in the chown command, some don't. There doesn't seem
> to be any logic behind which work and which result in "nobody" ownership.
>
> Example:
>
> # ls -l testfile
> -rw-r--r-- 1 nobody nobody 0 Oct 7 17:14 testfile
> # chown amy testfile
> # ls -l testfile
> -rw-r--r-- 1 amy nobody 0 Oct 7 17:14 testfile
> # chown sswowner testfile
> # ls -l testfile
> -rw-r--r-- 1 nobody nobody 0 Oct 7 17:14 testfile
>
> Group membership doesn't appear to be the issue, as some members of a group
> work and others don't.
>
> Suggestions? Places to start looking? I don't know if this is a passwd file
> issue, an nfs issue, a simplefs issue, or what.
>
> --
> Amy Skowronek Solar Data Analysis Center
> amy_at_aloha.nascom.nasa.gov NASA/Goddard Space Flight Center
>
>
Received on Fri Oct 08 1999 - 14:53:51 NZDT

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