linux sar logs

For Linux user operation records, the command history is generally used to view historical records. However, if important data is deleted due to misoperations, The history Command will not be useful. So how should we implement the historical operation records? In fact, we can log on to the IP address to record the historical operations of all user logon operations! The specific operation is to configure the configuration in/etc/profile. For

Log on to the IP address to record the logs of all Linux User Logon operations. For Linux user operation records, the command history is generally used to view the historical records. However, if the records are deleted due to misoperationsIn the case of important data, the history command will not be useful. What should we do if we still have historical operatio

Linux Log default time format: Dec 16 09:52:01, looks not accustomed to, modified to 2014-12-16 09:52:01 feel much more comfortable.Steps:Vi/etc/rsyslog.conf# define your own localized time format$template MyFormat, "% $NOW%%timestamp:8:15%%hostname%%syslogtag%%msg%\n"# Use default timestamp format# $ActionFileDefaultTemplate Rsyslog_traditionalfileformat# Use a custom format$ActionFileDefaultTemplate MyFormatRsyslog changing the time format for

=" alt= " File-read-4094.png "/>The 32-bit system uses the following command to resolve:Ln-s/usr/local/lib/libgeoip.so*/lib/The 64-bit system attempts to resolve using the following command:Ln-s/usr/local/lib/libgeoip.so*/lib64/Run the goaccess command again normally:650) this.width=650; "src=" Http://blog.cnezsoft.com/file-read-4095.png "width=" 643 "height=" 319 "alt=" File-read-4095.png "/>Goaccess using:Find the directory where the log file Access.log is located, the simplest and most straig

28245 [Note] innodb:using Linux native AIO2015-01-29 09:51:25 28245 [Note] innodb:not using CPU CRC32 instructions2015-01-29 09:51:25 28245 [Note] innodb:initializing buffer pool, size = 128.0M2015-01-29 09:51:25 28245 [Note] innodb:completed initialization of buffer pool2015-01-29 09:51:25 28245 [Note] innodb:the first specified data file./ibdata1 did not exist:a new database to be creat ed!2015-01-29 09:51:25 28245 [Note] innodb:setting file./ibdat

Tags: Linux basicsWe refer to inode blocks and block blocks as data storage areas or blocks of data, such as superblock, block blocks, inode bitmaps, etc., which are called intermediate or meta-data, because metadata changes frequently and there is a case of inconsistency with the actual data. So there is the file system log function.Ext3 File System log: First put a copy of the block to be written into the log, when the IO data sent to the log to the

Log on to the IP address to record the logs of all Linux user logon operations. for Linux user operation records, the command history is generally used to view the historical records, however, if important data is deleted due to misoperations, The history Command will not be useful. So there will still be history... Log on to the IP address to record the

MV *./html/PathCopy from local to remotescp/home/daisy/full.tar.gz [Email Protected]:/home/root (You will then be prompted to enter the login password of the root user of the other 172.19.2.75 host, and then the copy is copied), copy the directory plus the parameter-RCopy from remote to localSCP [Email protected]/172.19.2.75:/home/root/full.tar.gz/home/daisy/full.tar.gzPass folder with-R parameter otherwise there is not a regular file errorScp-r bdump [Email protected]:bdumpSSH [email protected]

the log dump parameters stored in the/ETC/LOGROTATE.D directory, which is useful when the RPM package is installed in the system. The log dump parameters for RPM packages are generally stored in the/ETC/LOGROTATE.D directory. # RPM Packages Drop log rotation information into this directory include/etc/logrotate.d# no packages own wtmp and btmp --we ' ll rotate them here/var/log/wtmp {monthly Create 0664 root utmp minsize 1M Rotate 1}/var/log/btmp {Missingok monthly create 0600 root utmp rotat

How to Use Xshell to view Tomcat real-time logs with Chinese garbled characters in Linux In Linux, when Xshell is used to view tomcat real-time logs, Chinese characters are garbled, but the Chinese characters in the log files are not garbled. There may be two reasons. The i18n of the system does not support Chinese ch

Tag: A hook script that allows users to modify Subversion logs (Linux)The programmer submits the code to SVN and discovers that the log error needs to be modified, but no permission error message "This repository does not allow modification of version properties, please administrator create Pre-revprop-change hooks"Follow the instructions, SVN server in the Linux

Today, when deploying a project to a Linux server, it has been an error, but there is no record in the log file. But there was no error in the local test, there was no error on the Windoesserver server, there was no reason to find it, so I wanted to see the running logs of Tomcat in real time.　　1, first switch to: cd usr/local/tomcat5/logs2-F Catalina.out3, so the runtime can view the running log in real ti

changes, exit VISet NuShow line NumbersOr?Find, enter what you are looking for in/afterNwith/or, if the search is not the keyword you are looking for, press N or backwards (with/to) or forward (with?) to continue looking until you find it.For the first use VI, there are a few notes to remind:1. When you open a file with VI, you are in command mode, and you want to switch to insert mode to enter text. Toggle method: Click on the letter "i" "Command mode" to enter "Insert Mode", then you can star

When logging SSH operation logs in Linux and logging on to the management host using ssh, you can save commands and outputs for ssh operation to the specified log file to facilitate subsequent viewing of operation logs. When logging on to the host through SSH, run the following command: Java code ssh username @ server | tee-a logfile.txt where the tee command rea

/var/log/cronLogs related to system timing tasks are logged/var/log/cupsLogs of printed information are logged/var/log/dmesgThe information of the kernel self-test in the system is recorded, and can be viewed directly by DMESG command./var/log/btmpLog errors logged, cannot be viewed directly, is a binary file, use the LASTB command to view/var/log/lastlogRecords the last logon time of all users in the system, cannot be viewed directly, is a binary file, use the Lastlog command to view/var/log/ma

divided into 5 parts.Postrotate/endscript: script executed after the log dump. This is used to let Nginx regenerate the log file. The nginx.pid is the main process number of nginx.Execution Logrotate: /usr/sbin/logrotate-vf/etc/logrotate.conf If there is no error, generated a dump file, Nginx normal access, OK.How the logrotate automatically executes:There are scripts executed by logrotate in the/etc/cron.daily directory. Executed once a day through the crontab program.This articl

PHP version: Copy codeThe Code is as follows :/** * Delete logs 7 days ago * @ Param $ logPath */ Function del7daysAgoLog ($ logPath ){ If (empty ($ logPath) return; $ Handle = opendir ($ logPath ); While ($ file = readdir ($ handle ))! = False ){ $ Pos = strpos ($ file, '. log '); If ($ pos! = False (strtotime ("-1 week")> fileatime ($ logPath. $ file ))){ Unlink ($ logPath. $ file ); } } } Shell versionCopy codeThe Code is as follows

Solution in windows: Find the path of session. save_path = "" in php. ini and check whether this directory exists or whether the directory has write permissions for everyone or Authenticated Users. Generally Solution in linux: After updating PHP today, the phpmyadmin configured in the result is logged in, "You cannot create a session when an error occurs. Check the PHP or website server logs and correc

Nagios (centreon) monitors Linux logs1. Download check_log3.pl and put it in the plug-in folder [root @ SSAVL2475 libexec] # cp/tmp/check_log3.pl/usr/local/nagios/libexec 2 to add execution permissions # chmod + x check_log3.pl [root @ SSAVL2475 libexec] # chmod + x check_log3.pl 3 modify owner # chown nagios. nagios check_log3.pl [root @ SSAVL2475 libexec] # chown nagios. nagios check_log3.pl 4 run check_log3.pl to confirm that it is executable. No e

2 Steps for Scheduled cleanup1. Find out the files that need to be cleaned2, the system to increase the scheduled execution of tasksFirst step , VI dellog.shStep Two , find the files you need to clean upInput: Find/var/log/nginx-mtime +7-type f-name \*.log | Xargs rm-fwhich-mtime +7 to find files 7 days agoHttp://blog.sina.com.cn/s/blog_716358dc0100lj5p.html-type F, type is fileHttp://zhidao.baidu.com/link?url=KH_ Fs6kqvwbcfsxfvha2cxi-193wbkztamsvr-gmgfvc7s-8ldpndpcjk6uzj6hzxcc47nwku7rcp7datxvsv