Chgrp failed on NAS mounted Post: 302894911

9 More Discussions You Might Find Interesting

1. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ...

2. UNIX for Dummies Questions & Answers

Chgrp and Chown ???

Hi Can anybody please let me know the usage of Chgrp command with an example??? Thanks

3. OS X (Apple)

AFP mount + Chown/Chgrp respecting

Hello all... Does anyone know how to make an AFP mount of home directories (/Volumes/users off of another server) so that any users doing an ssh login retain write permission to their individual folders, read-write permissions to folders chowned to appropriate group... and so that newly created...

4. Shell Programming and Scripting

Can't chgrp, chown on Linux

I have a problem on Linux wherein it doesn't allow me to use the chown and chgrp even if I am the owner of the file. Is this one of the Linux limitations? BTW, I can use chmod.

5. Shell Programming and Scripting

Check if NAS filesystem is mounted

Anyone know the best way to check and see if a NAS filesystem is mounted on a linux box. I have no idea where to start :wall:.

6. Solaris

how to make nas share mounted in zones persistent across reboots?

there are few nas shares that would be mounted on the local zone. should i add an entry into the add an entry in zone.xml file so that it gets mounted automatically when the zone gets rebooted? or whats the correct way to get it mounted automatically when the zone reboots

7. Red Hat

Can't chgrp. Error - chgrp: changing group of `<file>': Invalid argument

I found that I cannot chgrp for some reason with error: chgrp: changing group of `<file>': Invalid argument This happens on all NFS mounted disks on client machines. We use AD (not my call) for authentication and it also provides groups. We have a NFS server running Scientific Linux 6.3...

8. UNIX for Dummies Questions & Answers

Extremely slow file writing with many small files on mounted NAS

I am working on a CentOS release 6.4 server which has two mounted NAS devices, one with 20 x 3TB HDD running in FreeBSD with Zfs2 and one NAS which I don't know much about, but which has 7 HDDs in RAID-6. I was running tar -zxvf on a tarball that is 80Mb with 50,000 small files inside. Even...

9. Red Hat

Related to "NAS" some file system (mounted volumes) were not writable

Dear friends, I have been facing an issue with one of my red hat unix machine, suddenly lost to switch sudo users. My all colleagues lost to switch to access sudo users. Then, we have realized its related to NAS issue which does not allowing to write the file. because of this we got so many...

LEARN ABOUT DEBIAN

members

MEMBERS(1)						      General Commands Manual							MEMBERS(1)

NAME

       members - outputs members of a group

SYNOPSIS

       members groupname

DESCRIPTION

       This manual page documents briefly the members commands.  This manual page was written for the Debian GNU/Linux distribution.

       members is a program that sends a space-separated list of secondary member names to its standard output.

OPTIONS

       The  programs follow the usual GNU command line syntax, with long options starting with two dashes (`-').  A summary of options is included
       below.

       -a, --all
	      Show all group members on one line. This is the default.

       -p, --primary
	      Show only primary group members.

       -s, --secondary
	      Show only secondary group members.

       -t, --two-lines
	      Send two lines to standard output. First line is primary members, second line is secondary members. NOTE: This always  displays  two
	      lines, even if there are no members at all.

       -h, --help
	      Show summary of options.

DIAGNOSTICS

       Exit status is 0 (i.e. "success") if the group was found, and 1 (i.e., "failure") if the group was not found.

       Technically,  the  exit status hinges on the output of getgrnam(3) as follows: if getgrnam(3) returns a null pointer, the exit status is 1,
       and 0 otherwise.

BUGS

       I don't know of any! If you find one, please let me know!

SEE ALSO

       groups(1)

AUTHOR

       This manual page was written by Jim Lynch <jim@laney.edu>, for the Debian GNU/Linux system (but may be used by others).

																	MEMBERS(1)