I have created a shared directory on /home, where all users on a certain group have read, write and execute permissions.
I did this using
The problem is, when a particular user creates a directory within /home/shared, other users are not able to write to that directory. Is there a way to set the permissions such that all users within the group have full permissions in that directory?
Hello!
I want users in a certain group to be restricted to their home directory. So that they have full access to all files and folders in their home directory but the cant go to any directory above.
Does anyone know how to do this?
Anders (1 Reply)
I accidently reset the permissions of my /home/punkrockguy318 directory to root only. How can I get my punkrockguy318 permissions ( and all of it's contents) to be read/write accesable only to punkrockguy318 and root? (5 Replies)
Hi
I want to know which profile will be called when a user without home directory is created.
When I created a user without home directory(by setting in /etc/default/useradd), the user is able to login directly into the main "/" folder but with only read permissions.
Thanks
naina (3 Replies)
Hello All,
I have a new HPUX system going into production and it will be used by 2 projects. One of the contract requirements is the 2 groups can not have access to the others work or data. I believe I have the system pretty well locked up using groups and permissions and selective mounting of... (2 Replies)
Hi,
I am looking for a shell script (or any other way), that puts a user in a home directory jail. So for example, I have a user named richard and I don't want him wandering outside /usr/users/richard. I don't want him to cd to anywhere including cd ..
Somebody said you can do that with... (3 Replies)
I'm using HPUX 11i. The other day a user logon to the workstation and was not able to find the /home/directory (tom is the directory) I login myself and it is the same thing.
The home directory is on the server, so I was thinking of using sam to map it again. does anyone know how to do it... (5 Replies)
My users home directory located in a RHEL 5.0 nfs server.
Client is ubuntu 8.1 using NIS for authntication anf NFS for automounting
home Directory on the client side.
I set 700 to the users home directory.
My problem here is some of the users change the mode, which result in leak of... (2 Replies)
Hi Guys,
I have a problem with configuring a server. this is a solaris 10 with sparc platform.
I have setup so that the server is Authenticating through NIS but I dont want the server to Mount the Home directories. The users need to logged in through the CDE/display.
I have over 200 users... (2 Replies)
RHEL5.0
As we know, when root create a new user, a new home directory will be created : /home/user
I want to know what determine the access permission of /home/user .
Thanks! (1 Reply)
Hi friends,
I must to give ssh connection to own customer.
So I want to lock ssh user on own home directory. It is not necessery to reach other folders. I know that ftp user can lock on own folder but I don't know how to lock ssh user.
I am waitting your kindly helps :D
---------- Post... (10 Replies)
Discussion started by: getrue
10 Replies
LEARN ABOUT MOJAVE
strmode
STRMODE(3) BSD Library Functions Manual STRMODE(3)NAME
strmode -- convert inode status information into a symbolic string
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <string.h>
void
strmode(int mode, char *bp);
DESCRIPTION
The strmode() function converts a file mode (the type and permission information associated with an inode, see stat(2)) into a symbolic
string which is stored in the location referenced by bp. This stored string is eleven characters in length plus a trailing NUL.
The first character is the inode type, and will be one of the following:
- regular file
b block special
c character special
d directory
l symbolic link
p fifo
s socket
w whiteout
? unknown inode type
The next nine characters encode three sets of permissions, in three characters each. The first three characters are the permissions for the
owner of the file, the second three for the group the file belongs to, and the third for the ``other'', or default, set of users.
Permission checking is done as specifically as possible. If read permission is denied to the owner of a file in the first set of permis-
sions, the owner of the file will not be able to read the file. This is true even if the owner is in the file's group and the group permis-
sions allow reading or the ``other'' permissions allow reading.
If the first character of the three character set is an ``r'', the file is readable for that set of users; if a dash ``-'', it is not read-
able.
If the second character of the three character set is a ``w'', the file is writable for that set of users; if a dash ``-'', it is not
writable.
The third character is the first of the following characters that apply:
S If the character is part of the owner permissions and the file is not executable or the directory is not searchable by the owner, and
the set-user-id bit is set.
S If the character is part of the group permissions and the file is not executable or the directory is not searchable by the group, and
the set-group-id bit is set.
T If the character is part of the other permissions and the file is not executable or the directory is not searchable by others, and the
``sticky'' (S_ISVTX) bit is set.
s If the character is part of the owner permissions and the file is executable or the directory searchable by the owner, and the set-
user-id bit is set.
s If the character is part of the group permissions and the file is executable or the directory searchable by the group, and the set-
group-id bit is set.
t If the character is part of the other permissions and the file is executable or the directory searchable by others, and the ``sticky''
(S_ISVTX) bit is set.
x The file is executable or the directory is searchable.
- None of the above apply.
The last character will always be a space.
SEE ALSO chmod(1), find(1), stat(2), getmode(3), setmode(3)HISTORY
The strmode() function first appeared in 4.4BSD.
BSD July 28, 1994 BSD