02-03-2011
User creation (with only read only access)
I need to create a user with least permission on the production server.
He should only be able to read or execute the files that to be specific.
For example:
I just need to give him a set of commands to run.Besides those command execution He should be prevented to run any other command and He should not able to create any files(write permission).
How would i proceed about this.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm looking for a way to get the date of creation for a file. Is it possible ? I know that these informations are in the i-node but I don't know how to access them (if the 'find' command can do it with option -ctime, I have reasons to believe in it).
Thanks for helping me ! (1 Reply)
Discussion started by: mullmafr
1 Replies
2. UNIX for Dummies Questions & Answers
folks;
I created a new users on my SUSE box and i need to give this user/group a read write access to one specific folder. here's the details:
- I created new user "funny" under group "users".
- I need to give this user "funny" a read/write access to another directory that is owned by "root".... (3 Replies)
Discussion started by: Katkota
3 Replies
3. Red Hat
Hi
Thanks in advance.
How to create a user without useradd command ?? (1 Reply)
Discussion started by: krish4linux
1 Replies
4. Solaris
Hello guys,
i have a problem where i cant create a user and here some problem that i encounter.
1. /etc/passwd seems locked.
2. getting this error UX: useradd: ERROR: Cannot update system files - login cannot be created.
# useradd -u 47367 -g 1084 -c "user123" -d /local/home/user123 -s... (2 Replies)
Discussion started by: brew
2 Replies
5. Shell Programming and Scripting
hi,
how to create user name with read only access.
i think first need to create group with read only access after that i need to create the user and assign it to that group. If it is correct, how to create user with read only access? (4 Replies)
Discussion started by: rsivasan
4 Replies
6. AIX
hi seniors
i want to create the users like when the user try to login it should not
should not promt for passwd is it possible to create users like this
please help me (6 Replies)
Discussion started by: senmak
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
I want to create files and directories with below access control
System. AIX
File should have 664 permission
Directories should have 755
Can you please let me know how to achieve this? (3 Replies)
Discussion started by: balasubramani04
3 Replies
8. Solaris
Hi All,
I want to configure samba share permission so that only directory creator/owner has a read and write permission and other users should not have any read/write access to that folder.Will that be possible and how can this be achieved within samba configuration.
Regards,
Sahil (1 Reply)
Discussion started by: sahil_shine
1 Replies
9. Shell Programming and Scripting
Hi All,
I would have many files in the server with
xyz*.dat -- Static file name
Physical files:
xyz1.dat - 01PM
xyz2.dat - 02PM
xyz3.dat - 03PM
In present version we are using
for f in $file_name
do
fname=`ls $f | grep -v ^'\|'$ | sed s/' '/'\\ '/g`
....
sqlldr... (4 Replies)
Discussion started by: Dharv
4 Replies
sticky(5) Standards, Environments, and Macros sticky(5)
NAME
sticky - mark files for special treatment
DESCRIPTION
The sticky bit (file mode bit 01000, see chmod(2)) is used to indicate special treatment of certain files and directories. A directory for
which the sticky bit is set restricts deletion of files it contains. A file in a sticky directory can only be removed or renamed by a user
who has write permission on the directory, and either owns the file, owns the directory, has write permission on the file, or is a privi-
leged user. Setting the sticky bit is useful for directories such as /tmp, which must be publicly writable but should deny users permission
to arbitrarily delete or rename the files of others.
If the sticky bit is set on a regular file and no execute bits are set, the system's page cache will not be used to hold the file's data.
This bit is normally set on swap files of diskless clients so that accesses to these files do not flush more valuable data from the sys-
tem's cache. Moreover, by default such files are treated as swap files, whose inode modification times may not necessarily be correctly
recorded on permanent storage.
Any user may create a sticky directory. See chmod for details about modifying file modes.
SEE ALSO
chmod(1), chmod(2), chown(2), mkdir(2), rename(2), unlink(2)
BUGS
The mkdir(2) function will not create a directory with the sticky bit set.
SunOS 5.10 1 Aug 2002 sticky(5)