Hmm, a NAS server should know the users and groups.
If not, I do not have practical experience what exactly happens. NFSv3 might pass the request to the server, and the server denies it.
Or do you use NFSv4? To find out, please run
The automounter does not matter here.
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:
... (4 Replies)
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... (0 Replies)
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. (4 Replies)
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 (2 Replies)
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... (1 Reply)
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... (4 Replies)
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... (1 Reply)
Discussion started by: Chand
1 Replies
LEARN ABOUT DEBIAN
radwho
RADWHO(1) FreeRADIUS Daemon RADWHO(1)NAME
radwho - show online users
SYNOPSIS
radwho [-c] [-d raddb_directory] [-f] [-i] [-n] [-N nas_ip_address] [-p] [-P nas_port] [-r] [-R] [-s] [-S] [-u user] [-U user] [-Z]
DESCRIPTION
The FreeRADIUS server can be configured to maintain an active session database in a file called radutmp. This utility shows the content of
that session database.
OPTIONS -c Shows caller ID (if available) instead of the full name.
-d raddb_directory
The directory that contains the RADIUS configuration files. Defaults to /etc/raddb.
-f Behave as the 'fingerd' daemon - waits for one line of input, then prints the output with lines
terminated.
-i Shows the session ID instead of the full name.
-n Normally radwho looks up the username in the systems password file, and shows the full username as well. The -n flags prevents this.
-N nas_ip_address
Show only those entries which match the given NAS IP address.
-p Adds an extra column for the port type - I for ISDN, A for Analog.
-P nas_port
Show only those entries which match the given NAS port.
-r Outputs all data in raw format - no headers, no formatting, fields are comma-separated.
-R Output all data in RADIUS attribute format. All fields are printed.
-s Show full name.
-S Hide shell users. Doesn't show the entries for users that do not have a SLIP or PPP session.
-u user
Show only those entries which match the given username (case insensitive).
-U user
Show only those entries which match the given username (case sensitive).
-Z When combined with -R, prints out the contents of an Accounting-Request packet which can be passed to radclient, in order to "zap"
that users session from radutmp.
For example,
$ radwho -ZRN 10.0.0.1 | radclient -f - radius.example.net acct testing123
will result in all an Accounting-Request packet being sent to the RADIUS server, which tells the server that the NAS rebooted. i.e. It
"zaps" all of the users on that NAS.
To "zap" one user, specifiy NAS, username, and NAS port:
$ radwho -ZRN 10.0.0.1 -u user -P 10 | radclient -f - radius.example.net acct testing123
Other combinations are also possible.
SEE ALSO radiusd(8), radclient(1), radiusd.conf(5).
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl.
7 April 2005 RADWHO(1)