10 More Discussions You Might Find Interesting
1. HP-UX
As i know, Unix or Linux only manages 2 type of user: root user or normal user.
All users with userID=0 will have all administration permissions like root user with the system.
In my case, i want to create a new user in HP-UNIX environment with all root permissions only one exception that this... (5 Replies)
Discussion started by: hieucn1404
5 Replies
2. UNIX for Dummies Questions & Answers
I want to create a GROUP with rwx permission. Also, I want to create a GROUP with root privileges, so that next time i create a user, I just need to add it to any of the groups and privileges automatically applied.
please help.
Thanks,
Shouvanik (4 Replies)
Discussion started by: shouvanik
4 Replies
3. UNIX for Dummies Questions & Answers
Hi Guys,
I want to know is there any method to create a file having 777 permission. I am aware of umask, since it is only giving max. 666 permission for files this is not fulfilling my needs.
Thanks in advance
---------- Post updated at 12:49 AM ---------- Previous update was at 12:31... (10 Replies)
Discussion started by: sanoop
10 Replies
4. Solaris
is there a way to create a user and limit him to read,write and execute only in one direcotry.
the directory is already exsist and it belongs to dba group.
i would like to make this user can't even cd to another directory or even if he can he cant do anything in the other directories.
if... (7 Replies)
Discussion started by: q8devilish
7 Replies
5. Solaris
Hi All,
I want to create an user account which can only excute "df -kh" and "prstat -a" command. The user will not be able to perform "rm" and other critical commands.
Is there a way to do it?
rgds,
Ronny (2 Replies)
Discussion started by: ronny_nch
2 Replies
6. UNIX for Dummies Questions & Answers
dear guys,
sorry for asking a noob :p question, tried to search the forum for an answer but couldn't find one, i am running solaris 10 and i would like to create a user with limited access to view only one directory, the directory already exist, is this possible:confused:?
thanks and regards (4 Replies)
Discussion started by: q8devilish
4 Replies
7. Solaris
Hi,
I tried to search, but could not find answer for this really:
Is it possible to create a user that would have access only to a defined list of files? I would like to create a user that can access a set of files that are located behind different path. This user should not have access to... (1 Reply)
Discussion started by: Juha
1 Replies
8. UNIX for Advanced & Expert Users
i want to create unix user account (usera) for outsider so that they can run program that exist in /application/xxx/.
The account have their own home directory (/home/usera).
But on the same time the user cannot run any application/command either than in /application/xxx/.
User can only... (1 Reply)
Discussion started by: golden_shooter
1 Replies
9. UNIX for Dummies Questions & Answers
i want to create unix user account (usera) for outsider so that they can run program that exist in /application/xxx/.
The account have their own home directory (/home/usera).
But on the same time the user cannot run any application/command either than in /application/xxx/.
User can only... (1 Reply)
Discussion started by: golden_shooter
1 Replies
10. Solaris
Hi All,
I'm using solaris 2.8, and I want create a new ftp user account with the following restrictions:
- Have only ftp access, no telnet or rlogin
- Have restricted access to its home directory example /export/home/newuser
- Deny access to any other directory.
Thanks for your help,
... (6 Replies)
Discussion started by: Jeremy3
6 Replies
OPEN(5) File Formats Manual OPEN(5)
NAME
open, create - prepare a fid for I/O on an existing or new file
SYNOPSIS
Topen tag[2] fid[2] mode[1]
Ropen tag[2] fid[2] qid[8]
Tcreate tag[2] fid[2] name[28] perm[4] mode[1]
Rcreate tag[2] fid[2] qid[8]
DESCRIPTION
The open request asks the file server to check permissions and prepare a fid for I/O with subsequent read and write messages. The mode
field determines the type of I/O: 0, 1, 2, and 3 mean read access, write access, read and write access, and execute access, to be checked
against the permissions for the file. In addition, if mode has the OTRUNC (0x10) bit set, the file is to be truncated, which requires
write permission (if the file is append-only, and permission is granted, the open succeeds but the file will not be truncated); if the mode
has the ORCLOSE (0x40) bit set, the file is to be removed when the fid is clunked, which requires permission to remove the file from its
directory. If other bits are set in mode they will be ignored. It is illegal to write a directory, truncate it, or attempt to remove it
on close. If the file is marked for exclusive use (see stat(5)), only one client can have the file open at any time. That is, after such
a file has been opened, no other open will succeed until fid has been clunked. All these permissions are checked at the time of the open
request; subsequent changes to the permissions of files do not affect the ability to read, write, or remove an open file.
The create request asks the file server to create a new file with the name supplied, in the directory (dir) represented by fid, and
requires write permission in the directory. The owner of the file is the implied user id of the request, the group of the file is the same
as dir, and the permissions are the value of
(perm&(~0777|0111)) | (dir.perm&perm&0666)
if a regular file is being created and
(perm&~0777) | (dir.perm&perm&0777)
if a directory is being created. This means, for example, that if the create allows read permission to others, but the containing direc-
tory does not, then the created file will not allow others to read the file.
Finally, the newly created file is opened according to mode, and fid will represent the newly opened file. Mode is not checked against the
permissions in perm. The qid for the new file is returned with the create reply message.
Directories are created by setting the CHDIR bit (0x80000000) in the perm.
The names . and .. are special; it is illegal to create files with these names.
It is an error for either of these messages if the fid is already the product of a successful open or create message.
An attempt to create a file in a directory where the given name already exists will be rejected; in this case, the create system call (see
open(2)) uses open with truncation. The algorithm used by create is: first walk to the directory to contain the file. If that fails,
return an error. Next walk to the specified file. If the walk succeeds, send a request to open and truncate the file and return the
result, successful or not. If the walk fails, send a create message. If that fails, it may be because the file was created by another
process after the previous walk failed, so (once) try the walk and open again. For the behavior of create on a union directory, see
bind(2).
ENTRY POINTS
Open and create both generate open messages; only create generates a create message.
OPEN(5)