03-11-2019
We are not being obtuse, being overly literal, or blocking you. We're telling you that your question is nonsensical. You cannot stop root from being root. Period. Full stop. Any measures you use to stop them, they have full access to undo themselves, by definition.
For instance, useradd and userdel aren't magic -- they edit files. Block them and they can just edit the files by hand, or install something else for the purpose. Block access to the files and bad things will happen since the system needs these files.
You will have to approach the problem from another angle. Rather than 'limit what root can do', you will need to very precisely specify what they are actually allowed to do, and permit that in a non-root user via sudo.
These 5 Users Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to set up/modify a user account on one of our machines which will allow the user to stay on the system, but not use their user id and password to login to the machine. It is for the purposes of an ftp user, so that nobody can then login as ftp/passwd. Ta.:) (2 Replies)
Discussion started by: danhodges99
2 Replies
2. AIX
Hi all,
I am a newbe to aix 5.2. I want to specify the characters used by users while creating user in aix like specifying the length of the password
should i use some sript for that if it is then please let me know how to do this
if yes give me the link for the scripts.
Thanks in advance
... (2 Replies)
Discussion started by: Satya Mishra
2 Replies
3. UNIX for Dummies Questions & Answers
I created a user, i login as a root. I add him in the group where he can access and login as a root! I checked it in users' list and in group's list, he is there. My problem is this, I cant login using the username/account I just created! What should i do to use and login the user/account i've just... (5 Replies)
Discussion started by: jerome
5 Replies
4. Shell Programming and Scripting
Hi,
My requirement is that i am login from ROOT in a script but when any
command is coming which is logging to sqlplus then i have to run it with normal user as only normal user have permission to connect to sqlplus .
i tried making a script like this :
#! /bin/ksh
su -... (3 Replies)
Discussion started by: rawatds
3 Replies
5. Cybersecurity
Dears
I want to prevent users from doing spesific command "history -c" or "history" in general
How can I do ? (4 Replies)
Discussion started by: reaky
4 Replies
6. IP Networking
hi all,
i want to prevent users downloading files in the office as bandwidth becomes very low
and affects work.
one of my friend tried to close the connection using ethercap but this does not work.
i have a debian desktop while other users use MS W!ndows.
Please provide any help. Thanks (5 Replies)
Discussion started by: coolatt
5 Replies
7. Shell Programming and Scripting
Hi Every body,
I would need a shell script program to login as different user and perform some copy commands in the script.
example: Supppose ora_toms is the active user
ora_toms should be able to run a script where user: ftptomsp pass: XXX should login through and run the commands
... (9 Replies)
Discussion started by: ujjwal27
9 Replies
8. Shell Programming and Scripting
now i have logged in username : ramesh in unix
Now i have to created script file to login into another user and have run a command inside that user and after executing the command i have to exit from that user.
Inside script, i have to login into su - ram along with password : haihow and have to... (4 Replies)
Discussion started by: rammm
4 Replies
9. Shell Programming and Scripting
Hi could some let me know how to prevent user from changing his home directory.......
Thanks in advance.... (1 Reply)
Discussion started by: Revanth547
1 Replies
10. Shell Programming and Scripting
Hi could some let me know how to prevent user from changing his home directory.......
Thanks in advance.... (6 Replies)
Discussion started by: rahul547
6 Replies
LEARN ABOUT MOJAVE
edquota
EDQUOTA(8) BSD System Manager's Manual EDQUOTA(8)
NAME
edquota -- edit user quotas
SYNOPSIS
edquota [-u] [-p proto-username] username ...
edquota -g [-p proto-groupname] groupname ...
edquota -t [-u]
edquota -t -g
DESCRIPTION
Edquota is a quota editor. By default, or if the -u flag is specified, one or more users may be specified on the command line. For each
user a temporary file is created with an ASCII representation of the current disk quotas for that user. The list of filesystems with user
quotas is determined by scanning the mounted filesystems for a .quota.ops.user file located at its root. An editor is invoked on the ASCII
file. The editor invoked is vi(1) unless the environment variable EDITOR specifies otherwise.
The quotas may then be modified, new quotas added, etc. Setting a quota to zero indicates that no quota should be imposed. Setting a hard
limit to one indicates that no allocations should be permitted. Setting a soft limit to one with a hard limit of zero indicates that alloca-
tions should be permitted on only a temporary basis (see -t below). The current usage information in the file is for informational purposes;
only the hard and soft limits can be changed.
On leaving the editor, edquota reads the temporary file and modifies the binary quota files to reflect the changes made. The binary quota
file, .quota.user is stored at the root of the filesystem. The default filename and root location for the user quotas cannot be overridden.
If the -p flag is specified, edquota will duplicate the quotas of the prototypical user specified for each user specified. This is the nor-
mal mechanism used to initialize quotas for groups of users.
If the -g flag is specified, edquota is invoked to edit the quotas of one or more groups specified on the command line. The list of filesys-
tems with group quotas is determined by scanning the mounted filesystems for a .quota.ops.group file located at its root. Similarly, the
binary quota file, .quota.group is stored at the root of the filesystem. The default filename and root location for group quotas cannot be
overridden. The -p flag can be specified in conjunction with the -g flag to specify a prototypical group to be duplicated among the listed
set of groups.
Users are permitted to exceed their soft limits for a grace period that may be specified per filesystem. Once the grace period has expired,
the soft limit is enforced as a hard limit. The default grace period for a filesystem is specified in /usr/include/sys/quota.h. The -t flag
can be used to change the grace period. By default, or when invoked with the -u flag, the grace period is set for each filesystem with a
.quota.ops.user file located at its root. When invoked with the -g flag, the grace period is set for each filesystem with a .quota.ops.group
file located at its root. The grace period may be specified in days, hours, minutes, or seconds. Setting a grace period to zero indicates
that the default grace period should be imposed. Setting a grace period to one second indicates that no grace period should be granted.
Only the super-user may edit quotas.
FILES
Each of the following quota files is located at the root of the mounted filesystem. The mount option files are empty files whose existence
indicates that quotas are to be enabled for that filesystem. The binary data files will be created by edquota, if they don't already exist.
.quota.user data file containing user quotas
.quota.group data file containing group quotas
.quota.ops.user mount option file used to enable user quotas
.quota.ops.group mount option file used to enable group quotas
SEE ALSO
quota(1), quotactl(2), quotacheck(8), quotaon(8), repquota(8)
DIAGNOSTICS
Various messages about inaccessible files; self-explanatory.
BSD
June 1, 2019 BSD