linux audit file changes

Linux, as a multi-task and multi-user operating system, may be used by multiple users within the same period of time, and user management is directly related to the security of the entire system, users need to emphasize and protect password management and account file management. Linux User management is mainly divided into two aspects: password management and us

example, a program running in the object state can only execute non-privileged commands. Once the CPU encounters a privileged command, an illegal instruction error will occur. The processor status changes dynamically during system operation. Switching from the object state to the tube state can only be achieved through interruption. The conversion from the canonicalized state to the object state can be achieved by modifying the program State word psw

security has a great helpJ: When using the Ext3 file system format, setting the J property will cause the file to be recorded in the log when it is written, but when the filesystem setting parameter is data=journalled, the property is invalid because the log is already set.S: When the file is set to the s parameter, it will be completely removed from the hard di

Each file and directory in a Linux system has access permission to determine who can access and manipulate files and directories in any way. File or directory access is divided into read-only, write-only and executable three kinds. In the case of a file, read-only permission means that only its contents are allowed,

mode to deal with those who can not make changes in the case of logged-in users, the Runlevel number 1 can also be replaced with S. Runlevel 2 is a mode that allows the system to enter multiple users, but does not support file sharing, which is rarely applied. Runlevel 3 is the most common mode of operation, mainly used to provide true multiuser mode and the default mode for most servers. Runlevel

change, huh? That's not the truth. The first st_mtime refers to the file content changes, and st_ctime state refers to the file corresponding to the inode stored in the information changes, such as various permissions Ah, UID. GID and so on. So it's totally different.File name:Show in the final nature is the

file:Copy CodeThe code is as follows: Ls/etcThe ls-i command lists the entire directory file, the file name and inode number:Copy CodeThe code is as follows: Ls-i/etcIf you want to view the details of a file, you must access the Inode node based on the inode number and read the information. The ls-l command lists the details of the file.Copy CodeThe code is as f

that all examples included here are tested on SuSE Linux 8.0 professional. Although there is no reason to believe that they will not work on other systems, if there is a problem, you should check your documents to understand possible changes. Background Let's review some basic knowledge before going into the specifications. Files and commands In Linux/

Tags:. com-ini change name otherwise the first contains an objectEach file and directory in a Linux system has access permissions, which are used to determine who can access and manipulate files and directories.Access to a file or directory is divided into read-only, write-only, and executable three types. As an example of a