Shadowsocks-libev: 系统日志怎么关

[alex-888]

/var/log/message 和 journalctl 里好多ss的错误日志，可以关闭么

Dec 5 17:38:22 instance-1 /usr/bin/ss-server[17441]: failed to handshake with 144.10.15.207: authentication error
Dec 5 17:38:23 instance-1 /usr/bin/ss-server[17441]: failed to handshake with 144.10.15.207: authentication error
Dec 5 17:38:23 instance-1 /usr/bin/ss-server[17441]: failed to handshake with 144.10.15.207: authentication error
Dec 5 17:38:23 instance-1 /usr/bin/ss-server[17441]: failed to handshake with 144.10.15.207: authentication error

shadowsocks-libev.service

[Unit]
Description=Shadowsocks Server
After=network.target
[Service]
User=nobody
Group=nobody
Type=forking
PIDFile=/dev/shm/shadowsocks-libev.pid
ExecStart=/usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -f /dev/shm/shadowsocks-libev.pid
TTYPath=null
[Install]
WantedBy=multi-user.target

[oakaigh]

@a-l-e-x-6 A workaround is to redirect stderr messages to /dev/null;

replace ExecStart with the following

ExecStart=/usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -f /dev/shm/shadowsocks-libev.pid > /dev/null 2>&1

perform systemctl daemon-reload and then you are ready to go.

P.S. mask the IP address if it's yours; post the address to the hacking forum if you are confident that it's GFW's.

[alex-888]

@PantherJohn
no effect, still record error message

[cnJamesLucas]

ExecStart=/usr/bin/ss-server -c /etc/shadowsocks-libev/config.json -f /dev/shm/shadowsocks-libev.pid > /dev/null 2>&1

[oakaigh]

@cnJamesLucas @a-l-e-x-6 That’s right. I kinda ignored /dev/null while typing. Would fix it.