2. 程式人生 > >編譯bash實現history的syslog日誌記錄

編譯bash實現history的syslog日誌記錄

阿新 • • 發佈：2017-07-25
bash rpmbuild

一、下載bash源碼包 

[[email protected] other_x86_64]# http://vault.centos.org/6.9/os/Source/SPackages/bash-4.1.2-48.el6.src.rpm

二、安裝源碼包 

[[email protected] other_x86_64]# rpm -ivh bash-4.1.2-48.el6.src.rpm                               #警告可以忽略
1:bash                   warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
########################################### [100%]
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using roo

技術分享技術分享

[[email protected] ~]# ll
total 7208056
-rw-------. 1 root root       1891 Jul  7  2016 anaconda-ks.cfg
-rw-r--r--  1 root root    6686039 Jul 11  2016 bash-4.1.2-40.el6.src.rpm
-rw-r--r--. 1 root root      41443 Jul  7  2016 install.log
-rw-r--r--. 1 root root       7572 Jul  7  2016 install.log.syslog
drwxr-xr-x  8 root root       4096 Jul 11  2016 rpmbuild
[[email protected]
/* */ ~]# cd rpmbuild/ [[email protected] rpmbuild]# ll total 24 drwxr-xr-x 3 root root 4096 Jul 11 2016 BUILD drwxr-xr-x 2 root root 4096 Jul 11 2016 BUILDROOT drwxr-xr-x 3 root root 4096 Jul 11 2016 RPMS drwxr-xr-x 4 root root 4096 Jul 25 10:47 SOURCES drwxr-xr-x 2 root root 4096 Jul 25 10:47 SPECS drwxr-xr-x 2 root root 4096 Jul 11 2016 SRPMS

技術分享

三、重新編譯 

[[email protected] rpmbuild]# cd SOURCES/
[[email protected] SOURCES]# tar xf bash-4.1.tar.gz
[[email protected] SOURCES]# cp -a bash-4.1 bash-4.1-orig
[[email protected] SOURCES]# cd bash-4.1
[[email protected] bash-4.1]# vim config-top.h +104
/* #define SYSLOG_HISTORY */
#if defined (SYSLOG_HISTORY)
#  define SYSLOG_FACILITY LOG_USER
#  define SYSLOG_LEVEL LOG_INFO
#endif

技術分享

修改為

#define SYSLOG_HISTORY
#if defined (SYSLOG_HISTORY)
#  define SYSLOG_FACILITY LOG_LOCAL1
#  define SYSLOG_LEVEL LOG_DEBUG
#endif

技術分享

[[email protected] bash-4.1]# vim bashhist.c +701
void
bash_syslog_history (line)
const char *line;
{
char trunc[SYSLOG_MAXLEN];
if (strlen(line) < SYSLOG_MAXLEN)
syslog (SYSLOG_FACILITY|SYSLOG_LEVEL, "HISTORY: PID=%d UID=%d %s", getpid(), current_user.uid, line);
else
{
strncpy (trunc, line, SYSLOG_MAXLEN);
trunc[SYSLOG_MAXLEN - 1] = ‘\0‘;
syslog (SYSLOG_FACILITY|SYSLOG_LEVEL, "HISTORY (TRUNCATED): PID=%d UID=%d %s", getpid(), current_user.uid, trunc);
}
}

技術分享

修改為

void
bash_syslog_history (line)
const char *line;
{
char trunc[SYSLOG_MAXLEN];
if (strlen(line) < SYSLOG_MAXLEN)
 syslog (SYSLOG_FACILITY|SYSLOG_LEVEL, "HISTORY: PPID=%d PID=%d SID=%d UID=%d User=%s %s", getppid(),getpid(),getsid(getpid()),current_user.uid, current_user.user_name,line);
else
{
strncpy (trunc, line, SYSLOG_MAXLEN);
trunc[SYSLOG_MAXLEN - 1] = ‘\0‘;
syslog (SYSLOG_FACILITY|SYSLOG_LEVEL, "HISTORY (TRUNCATED): PPID=%d PID=%d SID=%d UID=%d User=%s %s", getppid(),getpid(),getsid(getpid()),current_user.uid,current_user.user_name,trunc);
}
}
#endif

技術分享

[[email protected] bash-4.1]# cd ..
[[email protected] SOURCES]# diff -Npru bash-4.1-orig bash-4.1 > bash_history_syslog.patch
[[email protected] SOURCES]# ls
bash-2.02-security.patch        bash-4.1-bind_int_variable.patch          bash-4.1-orig                                   bash-4.3-fix-terminate_immediately.patch
bash-2.03-paths.patch           bash-4.1-brace-expansion.patch            bash-4.1-posix-block-size-for-cf-options.patch  bash-4.3-read-sigterm.patch
bash-2.03-profile.patch         bash-4.1-broken_pipe.patch                bash-4.1-sighup-deadlock.patch                  bash-4.4-param-expansion.patch
bash-2.05a-interpreter.patch    bash-4.1-defer-sigchld-trap.patch         bash-4.1-signal.patch                           bash-bashbug.patch
bash-2.05b-debuginfo.patch      bash-4.1-enable-hyphened-fn-export.patch  bash-4.1-signal-sarestart.patch                 bash-cve-2016-9401.patch
bash-2.05b-manso.patch          bash-4.1-env-inject.patch                 bash-4.1.tar.gz                                 bash_history_syslog.patch
bash-2.05b-pgrp_sync.patch      bash-4.1-examples.patch                   bash-4.1-trap.patch                             bash-infotags.patch
bash-2.05b-readline-oom.patch   bash-4.1-extglob-man.patch                bash-4.2-1207042-double-alloc.patch             bash-requires.patch
bash-2.05b-xcc.patch            bash-4.1-fd-leaks.patch                   bash-4.2-1240994-case-in-command-subst.patch    bash-setlocale.patch
bash-3.2-audit.patch            bash-4.1-here-strings.patch               bash-4.2-1250070-ifs-in-temp-env.patch          bash-sighup.patch
bash-3.2-ssh_source_bash.patch  bash-4.1-history-hang.patch               bash-4.2-1260568-bash-debugger.patch            bash-tty-tests.patch
bash-4.0-nobits.patch           bash-4.1-logout.patch                     bash-4.2-cve-2014-7169-0.patch                  dot-bash_logout
bash-4.1                        bash-4.1-loop-bracket-comsub.patch        bash-4.2-cve-2014-7169-1.patch                  dot-bash_profile
bash41-001                      bash-4.1-manpage.patch                    bash-4.2-cve-2014-7169-2.patch                  dot-bashrc
bash41-002                      bash-4.1-manpage_trap.patch               bash-4.2-param-subst-mem-leak.patch
bash41-016                      bash-4.1-mem-leaks.patch                  bash-4.3-cve-2016-0634.patch
bash41-017                      bash-4.1-noecho.patch                     bash-4.3-cve-2016-7543.patch
[[email protected] SOURCES]# cd ..
[[email protected] rpmbuild]# cd SPECS/
[[email protected] SPECS]# ls
bash.spec
[[email protected] SPECS]# vim bash.spec
# Other patches
Patch101: bash-2.02-security.patch
Patch102: bash-2.03-paths.patch
Patch103: bash-2.03-profile.patch
Patch104: bash-2.05a-interpreter.patch
Patch105: bash-2.05b-debuginfo.patch
Patch106: bash-2.05b-manso.patch
Patch107: bash-2.05b-pgrp_sync.patch
Patch108: bash-2.05b-readline-oom.patch
Patch109: bash-2.05b-xcc.patch
Patch110: bash-3.2-audit.patch
Patch112: bash-3.2-ssh_source_bash.patch
Patch113: bash-bashbug.patch
Patch115: bash-infotags.patch
Patch116: bash-requires.patch
Patch117: bash-setlocale.patch
Patch118: bash-tty-tests.patch
Patch119: bash_history_syslog.patch                                   #增加的內容
......
# Other patches
%patch101 -p1 -b .security
%patch102 -p1 -b .paths
%patch103 -p1 -b .profile
%patch104 -p1 -b .interpreter
%patch105 -p1 -b .debuginfo
%patch106 -p1 -b .manso
%patch107 -p1 -b .pgrp_sync
%patch108 -p1 -b .readline_oom
%patch109 -p1 -b .xcc
%patch110 -p1 -b .audit
%patch112 -p1 -b .ssh_source_bash
%patch113 -p1 -b .bashbug
%patch115 -p1 -b .infotags
%patch116 -p1 -b .requires
%patch117 -p1 -b .setlocale
%patch118 -p1 -b .tty_tests
%patch119 -p1 -b .history_syslog                                                                                               #增加的內容
%patch123 -p1 -b .nobits
%patch124 -p1 -b .examples
%patch125 -p1 -b .bind_int_variable
%patch126 -p1 -b .broken_pipe
%patch127 -p1 -b .manpage
%patch128 -p1 -b .defer-sigchld-trap

技術分享技術分享

[[email protected] ~]# yum install texinfo                               #在另一窗口安裝
[[email protected] SPECS]# rpmbuild -ba bash.spec
+ exit 0
Processing files: bash-4.1.2-48.el6.x86_64
Provides: config(bash) = 4.1.2-48.el6
Requires(interp): /bin/sh
Requires(rpmlib): rpmlib(BuiltinLuaScripts) <= 4.2.2-1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(post): ncurses-libs
Requires(postun): /bin/sh
Requires: /bin/sh libc.so.6()(64bit) libc.so.6(GLIBC_2.11)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.4)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libtinfo.so.5()(64bit) rtld(GNU_HASH)
Processing files: bash-doc-4.1.2-48.el6.x86_64
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: /bin/bash /bin/sh
Processing files: bash-debuginfo-4.1.2-48.el6.x86_64
Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/bash-4.1.2-48.el6.x86_64
Wrote: /root/rpmbuild/SRPMS/bash-4.1.2-48.el6.src.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/bash-4.1.2-48.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/bash-doc-4.1.2-48.el6.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/bash-debuginfo-4.1.2-48.el6.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0zbnT0
+ umask 022
+ cd /root/rpmbuild/BUILD
+ cd bash-4.1
+ rm -rf /root/rpmbuild/BUILDROOT/bash-4.1.2-48.el6.x86_64
+ exit 0

技術分享

四、重新安裝bash

[[email protected] rpmbuild]# cd RPMS
[[email protected] RPMS]# ll
total 4
drwxr--r-- 2 root root 4096 Jul 25 13:08 x86_64
[[email protected] RPMS]# cd x86_64/
[[email protected] x86_64]# ll
total 5128
-rw-r--r-- 1 root root 931232 Jul 25 13:08 bash-4.1.2-48.el6.x86_64.rpm
-rw-r--r-- 1 root root 1374956 Jul 25 13:08 bash-debuginfo-4.1.2-48.el6.x86_64.rpm
-rw-r--r-- 1 root root 2939332 Jul 25 13:08 bash-doc-4.1.2-48.el6.x86_64.rpm
[[email protected] x86_64]# rpm -Uvh --force bash-4.1.2-48.el6.x86_64.rpm
Preparing... ########################################### [100%]
1:bash ########################################### [100%]

技術分享

技術分享


五、配置rsyslog日誌服務

[[email protected] x86_64]# cat /etc/rsyslog.conf
local1.debug                                                                /var/log/bash_history.log

技術分享

[[email protected] x86_64]# tail -f /var/log/bash_history.log
Jul 25 13:10:28 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root cd x86_64/
Jul 25 13:10:30 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root ll
Jul 25 13:12:57 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root bash --version
Jul 25 13:13:46 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root rpm -Uvh --force bash-4.1.2-48.el6.x86_64.rpm
Jul 25 13:13:49 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root ll
Jul 25 13:15:04 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root cp bash-4.1.2-48.el6.x86_64.rpm /var/repo/other_x86_64/
Jul 25 13:15:17 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root cat /etc/rsyslog.conf
Jul 25 13:15:33 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root ll /var/log/bash_history.log
Jul 25 13:15:48 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root more /var/log/bash_history.log
Jul 25 13:16:19 repo -bash: HISTORY: PPID=29829 PID=29831 SID=29831 UID=0 User=root tail -f /var/log/bash_history.log
Jul 25 13:16:30 repo -bash: HISTORY: PPID=5208 PID=5210 SID=5210 UID=0 User=root ll

技術分享

編譯bash實現history的syslog日誌記錄

相關推薦

編譯bash實現history的syslog日誌記錄

bash rpmbuild一、下載bash源碼包 [[email protected]/* */ other_x86_64]# http://vault.centos.org/6.9/os/Source/SPackages/bash-4.1.2-48.el6.src.rpm二、安裝源碼包 [[em

python實現AOP日誌記錄

前言 在Java中，AOP程式設計是一件比較通用方法，能夠少寫很多重複性的程式碼，讓程式自動幫我們完成，例如收集錯誤記錄，保證業務的事務性，無措提交，有錯回滾等。 最近寫了較多python程式碼，在python中，使用print 記錄日誌，但是每一個方法都要寫，比較麻煩，並且又不

實現錯誤日誌記錄

要實現錯誤日誌記錄，當有新的錯誤日誌產生時，能第一時間在新檔案中記錄下來。 這裡以nginx錯誤日誌為例， 內容如下： #!/bin/bash ##This script is used for log alerts a=`grep "error" /usr/local/n

SpringBoot通過AOP實現系統日誌記錄（三）-Mapper層日誌監控及自定義異常攔截

本文是SpringBoot通過AOP實現系統日誌記錄（三）-Mapper層日誌監控及異常攔截，若要實現Service層監控，請點選傳送門： SpringBoot通過AOP實現系統日誌記錄（二）-Service層日誌監控 由於公司業務上的需求，現在需要對整個系統做日誌效能監控，方便開發人員快速

Spring Aop實現簡單日誌記錄

日誌類 package com.jusfoun.estate.log.domain; import java.io.Serializable; import java.math.BigDecimal; import java.util.Date; import java

.NET Core微服務之基於Exceptionless實現分散式日誌記錄

一、Exceptionless極簡介紹 　　Exceptionless 是一個開源的實時的日誌收集框架，它可以應用在基於 ASP.NET，ASP.NET Core，Web API，Web Forms，WPF，Console，ASP.NET MVC 等技術開發的應用程式中，並且提供了REST介面可以應

android上如何實現後臺日誌記錄並寫檔案到sd卡

對於安卓的日誌，我們通常的做法是通過 第三方的平臺來實現日誌的儲存，例如騰訊的Buglay 和友盟統計 來實現，這些方法可以幫我們快速的統計各種bug以及其他資訊，但是至少有一點不太好就是當涉及到一些隱私的資訊不希望暴露在第三方平臺（基於安卓控制系統的APP），

java使用動態代理來實現AOP(日誌記錄)的例項程式碼

下面是一個AOP實現的簡單例子： 首先定義一些業務方法： 複製程式碼程式碼如下: /**  * Created with IntelliJ IDEA.  * Author: wangjie  email:[email protected]  * Date: 13-9-23  * T

Spring AOP自定義註解實現系統日誌記錄管理

package com.kilomob.powernetwork.managerweb.annotation; import java.lang.reflect.Method; import java.net.InetAddress; import java.util.Arrays; import java

.Net Core中介軟體和過濾器實現錯誤日誌記錄

1.中介軟體的概念 ASP.NET Core的處理流程是一個管道，中介軟體是組裝到應用程式管道中用來處理請求和響應的元件。 每個中介軟體可以： 選擇是否將請求傳遞給管道中的下一個元件。 可以在呼叫管道中的下一個元件之前和之後執行業務邏輯。 　　中介軟體是一個請求委託（ 

在CentOS6上編譯安裝實現LAMP（php-modules）+phpMyAdmin安裝過程全記錄

輸出 dev 補充 server log tab cif web 必須 php與apache協作有三種模式：CGI、modules、FastCGI。　　在CGI模式下，用戶請求php文件時，apache會啟動響應進程，調用php處理器處理請求，然後將結果返回給客戶端。用

將日誌記錄在是mysql中，實現loganalyzer

mysql 日誌 報表 三臺主機 192.168.191.106（代號106） 產生日誌 192.168.191.107（代號107） 實現存放日誌的數據庫 192.168.191.173（代號173） 實現日誌報表 1、實現rsyslog將日誌記錄於M

【C#】WebApi 添加過濾器，實現對請求參數和響應內容的日誌記錄

total exc gpo start ID json clear block pub filter的介紹 filter在Web API中經常會用到，主要用於記錄日誌，安全驗證，全局錯誤處理等；Web API提供兩種過濾器的基本類型：actionfilterattri

python內置函數print輸出到文件,實現日誌記錄的功能

imp inpu 函數 rgs print top args txt war # bulid time 2018-6-22 import os import time def log(*args, **kwargs): # *kargs 為了通用 可不傳 ru

oracle通過觸發器實現登錄登出日誌記錄

not contex lose 自動 begin val then sys tab -----刪除表--- drop table userlogininfo --創建登錄登出記錄信息表 create table userlogininfo ( infoid int pr

springboot—spring aop 實現系統操作日誌記錄存儲到數據庫

work prop 請求 pack spa 成功 方法 代碼 shu 原文：https://www.jianshu.com/p/d0bbdf1974bd 采用方案： 使用spring 的 aop 技術切到自定義註解上，針對不同註解標誌進行參數解析，記錄日誌

使用Spring AOP自定義註解方式實現使用者操作日誌記錄

1，開發環境 作業系統：Windows 7 JDK：1.8.0_161 Eclipse：Mars.2 Release (4.5.2) 2，自定義註解類UserLog @Target({ElementType.PARAMETER, ElementType.METHOD}) @R

C#實現日誌記錄 支援按日期多檔案儲存

日誌記錄類LogHelper,支援按照日期儲存，儲存的資訊帶時間資訊，具體的日誌內容如下： 2016-12-08 23:56:45:787 [Notice]sadfsafasfffffffffffffffffffffffffffffffffffffffff 2016-12-08 2

Springboot 如何使用AOP同時織入多個切面？實現使用者 操作日誌記錄功能

首先匯入AOP的pom <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-sta

springboot aop 自定義註解方式實現一套完善的日誌記錄（完整原始碼）

一：功能簡介 本文主要記錄如何使用aop切面的方式來實現日誌記錄功能。 主要記錄的資訊有: 操作人，方法名，引數，執行時間，操作型別(增刪改查)，詳細描述，返回值。 二：專案結構圖 三：MAVEM依賴 本專案有兩個pom檔案,父類的pom檔案主要作用是對子類pom檔案依賴的版本號進行統一管理。 1.最外層