Kr328

# Attribute: userinfo-url={{print .subscribe_url}}
# Attribute: filename={{hostOf .subscribe_url}}.yaml

ipv6: true
mixed-port: 7890
mode: rule
allow-lan: true
log-level: info
external-controller: 127.0.0.1:6170

weaponwang

函数签名：

long long stoll (const string&  str, size_t* idx = 0, int base = 10);
// linux 环境下应该很少能用到
long long stoll (const wstring& str, size_t* idx = 0, int base = 10); 

功能:

antirez

RESP3 specification

Versions history:

• 1.0, 2 May 2018, Initial draft to get community feedbacks.

Background

The Redis protocol has served us well in the past years, showing that, if carefully designed, a simple human readable protocol is not the bottleneck in the client server communication, and that the simplicity of the design is a major advantage in creating a healthy client libraries ecosystem.

Yet the Redis experience has shown that after about six years from its introduction (when it replaced the initial Redis protocol), the current RESP protocol could be improved, especially in order to make client implementations simpler and to support new features.

ageis

security and hardening options for systemd service units

A common and reliable pattern in service unit files is thus:

NoNewPrivileges=yes
PrivateTmp=yes
PrivateDevices=yes
DevicePolicy=closed
ProtectSystem=strict

nerdalert

Linux NetFilter, IP Tables and Conntrack Diagrams

IPTABLES TABLES and CHAINS

IPTables has the following 4 built-in tables.

1) Filter Table

Filter is default table for iptables. So, if you don’t define you own table, you’ll be using filter table. Iptables’s filter table has the following built-in chains.