


How to set up a CentOS system to restrict user modifications to system logs
How to set up the CentOS system to restrict users from modifying the system log
In the CentOS system, the system log is a very important information source. It records the system's operating status, error messages, warnings, etc. In order to protect the stability and security of the system, we should restrict users from modifying system logs. This article will introduce how to set up the CentOS system to restrict the modification permissions of the system log.
1. Create user groups and users
First, we need to create a user group specifically responsible for managing system logs, and an ordinary user for managing logs. Assume that the group name we created is logadmin and the user is loguser. It can be created through the following command:
sudo groupadd logadmin sudo useradd -g logadmin loguser
2. Modify the permissions of the log file
Next, we need to modify the permissions of the system log file so that Only users in the logadmin group can modify it, and other users can only read it. Usually, the log files of the CentOS system are located in the /var/log directory. Taking the system log file /var/log/messages as an example, we can execute the following command to modify the permissions:
sudo chown root:logadmin /var/log/messages sudo chmod 640 /var/log/messages
The above command will change the permissions of the log file. The owner is set to the root user, the group to which it belongs is set to the logadmin group, and the permissions are set to 640. In this way, only the root user and users belonging to the logadmin group can modify the log file, and other users can only read it.
3. Configure sudo permissions
In order to ensure that only users in the logadmin group have permission to modify log files, we also need to configure sudo permissions to restrict only users in the logadmin group from using specific commands. Suppose we want to restrict the loguser user to only use the logrotate command, we can perform the following steps:
Use the visudo command to edit the sudoers file:
sudo visudo
Copy after loginAdd the following content to the file:
%logadmin ALL=(ALL) NOPASSWD: /usr/sbin/logrotate
Copy after loginThis way, only users belonging to the logadmin group can use the logrotate command and no password is required.
4. Test settings
After completing the above settings, we can test whether the user's permission to modify the system log has been successfully restricted.
Switch to the loguser user:
sudo su - loguser
Copy after loginTry to modify the log file:
echo "test" >> /var/log/messages
Copy after loginCopy after loginSince the loguser user does not belong to the logadmin group, Therefore, the log file cannot be modified, and a message indicating insufficient permissions will be displayed.
Use the logadmin user to try to modify the log file:
echo "test" >> /var/log/messages
Copy after loginCopy after loginSince the logadmin user belongs to the logadmin group, it has the permission to modify the log file.
Through the above settings, we have successfully restricted the user's permission to modify the system log and protected the stability and security of the system.
Summary
This article introduces how to set up the CentOS system to restrict users' permission to modify system logs. By creating user groups and users, modifying permissions on log files, and configuring sudo permissions, we can achieve that only specific users can modify system logs and enhance system security and stability.Note: The group names, users and log files used in the examples in this article are for reference only and should be adjusted according to the actual situation in actual use.
The above is the detailed content of How to set up a CentOS system to restrict user modifications to system logs. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Backup and Recovery Policy of GitLab under CentOS System In order to ensure data security and recoverability, GitLab on CentOS provides a variety of backup methods. This article will introduce several common backup methods, configuration parameters and recovery processes in detail to help you establish a complete GitLab backup and recovery strategy. 1. Manual backup Use the gitlab-rakegitlab:backup:create command to execute manual backup. This command backs up key information such as GitLab repository, database, users, user groups, keys, and permissions. The default backup file is stored in the /var/opt/gitlab/backups directory. You can modify /etc/gitlab

The CentOS shutdown command is shutdown, and the syntax is shutdown [Options] Time [Information]. Options include: -h Stop the system immediately; -P Turn off the power after shutdown; -r restart; -t Waiting time. Times can be specified as immediate (now), minutes ( minutes), or a specific time (hh:mm). Added information can be displayed in system messages.

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Improve HDFS performance on CentOS: A comprehensive optimization guide to optimize HDFS (Hadoop distributed file system) on CentOS requires comprehensive consideration of hardware, system configuration and network settings. This article provides a series of optimization strategies to help you improve HDFS performance. 1. Hardware upgrade and selection resource expansion: Increase the CPU, memory and storage capacity of the server as much as possible. High-performance hardware: adopts high-performance network cards and switches to improve network throughput. 2. System configuration fine-tuning kernel parameter adjustment: Modify /etc/sysctl.conf file to optimize kernel parameters such as TCP connection number, file handle number and memory management. For example, adjust TCP connection status and buffer size

Steps to configure IP address in CentOS: View the current network configuration: ip addr Edit the network configuration file: sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0 Change IP address: Edit IPADDR= Line changes the subnet mask and gateway (optional): Edit NETMASK= and GATEWAY= Lines Restart the network service: sudo systemctl restart network verification IP address: ip addr

Common problems and solutions for Hadoop Distributed File System (HDFS) configuration under CentOS When building a HadoopHDFS cluster on CentOS, some common misconfigurations may lead to performance degradation, data loss and even the cluster cannot start. This article summarizes these common problems and their solutions to help you avoid these pitfalls and ensure the stability and efficient operation of your HDFS cluster. Rack-aware configuration error: Problem: Rack-aware information is not configured correctly, resulting in uneven distribution of data block replicas and increasing network load. Solution: Double check the rack-aware configuration in the hdfs-site.xml file and use hdfsdfsadmin-printTopo

The key to installing MySQL elegantly is to add the official MySQL repository. The specific steps are as follows: Download the MySQL official GPG key to prevent phishing attacks. Add MySQL repository file: rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm Update yum repository cache: yum update installation MySQL: yum install mysql-server startup MySQL service: systemctl start mysqld set up booting

Building a Hadoop Distributed File System (HDFS) on a CentOS system requires multiple steps. This article provides a brief configuration guide. 1. Prepare to install JDK in the early stage: Install JavaDevelopmentKit (JDK) on all nodes, and the version must be compatible with Hadoop. The installation package can be downloaded from the Oracle official website. Environment variable configuration: Edit /etc/profile file, set Java and Hadoop environment variables, so that the system can find the installation path of JDK and Hadoop. 2. Security configuration: SSH password-free login to generate SSH key: Use the ssh-keygen command on each node
