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(2) System Calls Manual OPEN(2)
NAME
open, create, close - open a file for reading or writing, create file
SYNOPSIS
#include <u.h>
#include <libc.h>
int open(char *file, int omode)
int create(char *file, int omode, ulong perm)
int close(int fd)
DESCRIPTION
Open opens the file for I/O and returns an associated file descriptor. Omode is one of OREAD, OWRITE, ORDWR, or OEXEC, asking for permis-
sion to read, write, read and write, or execute, respectively. In addition, there are three values that can be ORed with the omode: OTRUNC
says to truncate the file to zero length before opening it; OCEXEC says to close the file when an exec(2) or execl system call is made; and
ORCLOSE says to remove the file when it is closed (by everyone who has a copy of the file descriptor). Open fails if the file does not
exist or the user does not have permission to open it for the requested purpose (see stat(2) for a description of permissions). The user
must have write permission on the file if the OTRUNC bit is set. For the open system call (unlike the implicit open in exec(2)), OEXEC is
actually identical to OREAD.
Create creates a new file or prepares to rewrite an existing file, opens it according to omode (as described for open), and returns an
associated file descriptor. If the file is new, the owner is set to the userid of the creating process group; the group to that of the
containing directory; the permissions to perm ANDed with the permissions of the containing directory. If the file already exists, it is
truncated to 0 length, and the permissions, owner, and group remain unchanged. The created file is a directory if the CHDIR bit is set in
omode. It is an exclusive-use file if the CHEXCL bit is set. Such files may be open for I/O by only one client at a time, but the file
descriptor may become invalid if no I/O is done for an extended period; see open(5).
Create fails if the path up to the last element of file cannot be evaluated, if the user doesn't have write permission in the final direc-
tory, or if the file already exists and does not permit the access defined by omode. If the file is new and the directory in which it is
created is a union directory (see intro(2)) then the constituent directory where the file is created depends on the structure of the union:
see bind(2).
Close closes the file associated with a file descriptor. Provided the file descriptor is a valid open descriptor, close is guaranteed to
close it; there will be no error. Files are closed automatically upon termination of a process; close allows the file descriptor to be
reused.
SOURCE
/sys/src/libc/9syscall
SEE ALSO
intro(2), bind(2), stat(2)
DIAGNOSTICS
These functions set errstr.
OPEN(2)