因项目使用 maven 管理，并使用 maven-assembly-plugin 打包。可以在项目 pom.xml 中 maven-assembly-plugin 的配置下增加第二个打包配置文件。
<!-- The configuration of maven-assembly-plugin -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.4.1</version>
<!-- The configuration of the plugin -->
<configuration>
<finalName>your-app</finalName>
<!-- append assembly id in release file name -->
<appendAssemblyId>true</appendAssemblyId>
<!-- Specifies the configuration file of the assembly plugin -->
<descriptors>
<descriptor>src/main/assembly/bin.xml</descriptor>
<descriptor>src/main/assembly/docker.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
常规编写即可，没什么特殊要求。
<assembly>
<id>docker</id>
<formats>
<format>zip</format>
</formats>
<dependencySets>
</dependencySets>
<fileSets>
<fileSet>
<directory>${project.basedir}/target</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>*.zip</include>
</includes>
</fileSet>
<fileSet>
<directory>${project.basedir}</directory>
<outputDirectory>.</outputDirectory>
<includes>
<include>Dockerfile</include>
</includes>
</fileSet>
</fileSets>
</assembly>
编译
cd /builds
tar zxf /path/to/glibc-2.14.1.tar.gz
cd /builds/glibc-2.14.1
mkdir build
cd build
../configure --prefix=/opt/glibc/2.14.1
sudo apt-get install gawk # 解决 make 报错
make -j4
sudo make install
修改系统链接指向新动态库
cd /lib/x86_64-linux-gnu
unlink libc.so.6
ln -s /opt/glibc/2.14.1/lib/libc-2.14.1.so libc.so.6 # 命令报错，提示找不到 libc.so.6，其它好多系统内置命令也无法运行
执行以下命令
LD_PRELOAD=/lib/x86_64-linux-gnu/libc-2.13.so ln -s /opt/glibc/2.14.1/lib/libc-2.14.1.so libc.so.6
或
LD_PRELOAD=/opt/glibc/2.14.1/lib/libc-2.14.1.so ln -s /opt/glibc/2.14.1/lib/libc-2.14.1.so libc.so.6
推荐使用第 2 种方法。
在单元格内填入第一个手机号码 18900000001
在菜单中选择“编辑”->“填充”->“序列”
在弹出的窗口中，序列产生在选择“列”，类型选择“等差数列”，步长值填写“1”，终止值填写“18900080000“，点击确定按钮
序列填充完成后，可以看到，第一个值为 18900000001，最后一个值为 18900080000
但是，当我们要通过本地浏览器访问某台内网主机上的 web 程序（或通过数据库客户端访问某台内网主机上的数据库）时，要如何做呢？
一种可靠的方法是通过端口转发（映射），架构示意图如下：
具体可以通过 SecureCrt 或 Xshell 实现，具体方法如下：
确定连接跳板机或中转机的端口（当使用安全网关程序登录时，端口是随机的），可以看出 port 是 3551
新建一个会话，ip 127.0.0.1，端口 3551，并将所有的端口转发（映射）都配置上
连接刚建立的会话，连接成功后，就可以通过本机访问 web 程序或数据库了
http://127.0.0.106:8080/
jdbc:mysql://127.0.0.15:3306?test
Xshell 操作和 SecureCrt 类似，不再赘述。
跳板机或中转机连接关闭后，端口转发（映射）全部失效。
]]>chage 命令用法如下
user@server:~$ chage -h
Usage: chage [options] LOGIN
Options:
-d, --lastday LAST_DAY set date of last password change to LAST_DAY
-E, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
-h, --help display this help message and exit
-I, --inactive INACTIVE set password inactive after expiration
to INACTIVE
-l, --list show account aging information
-m, --mindays MIN_DAYS set minimum number of days before password
change to MIN_DAYS
-M, --maxdays MAX_DAYS set maximim number of days before password
change to MAX_DAYS
-R, --root CHROOT_DIR directory to chroot into
-W, --warndays WARN_DAYS set expiration warning days to WARN_DAYS
其中，-E 设置账号过期时间，-M 设置密码过期时间，-I 设置密码失效时间。
用户 user 查看自己账号和密码的有效期
user@server:~$ chage -l user
Last password change : Nov 28, 2016
Password expires : never
Password inactive : never
Account expires : never
Minimum number of days between password change : -1
Maximum number of days between password change : 99999
Number of days of warning before password expires : 7
设置账号 user 的过期时间为 2018 年 12 月 31 日
root@server:~# chage -E "2018-12-31" user
设置账号 user 永不过期
root@server:~# chage -E -1 user
设置账号 user 立即过期
root@server:~# chage -E 0 user
设置账号 user 的密码在 MAX_DAYS=30 天后过期，此时必须先修改密码才能登录系统
root@server:~# chage -M 30 user
设置账号 user 的密码在 MAX_DAYS+3 天后失效，此时不能登录系统，只能求助于管理员
root@server:~# chage -I 3 user
http://download.redis.io/releases/redis-3.2.11.tar.gz
tar zxvf redis-3.2.11.tar.gz
cd ~/redis-3.2.11
make
创建集群目录，将编译好的命令文件复制到 bin 目录
mkdir -p /usr/local/redis-cluster/bin
cd ~/redis-3.2.11/src
cp mkreleasehdr.sh redis-benchmark redis-check-aof redis-check-dump redis-cli redis-server redis-trib.rb /usr/local/redis-cluster/bin
创建 6 个 redis 实例目录，并将 redis 配置文件复制到各实例目录
cd /usr/local/redis-cluster
mkdir -p 9001/data
mkdir -p 9002/data
mkdir -p 9003/data
mkdir -p 9004/data
mkdir -p 9005/data
mkdir -p 9006/data
cp ~/redis-3.2.11/redis.conf 9001
cp ~/redis-3.2.11/redis.conf 9002
cp ~/redis-3.2.11/redis.conf 9003
cp ~/redis-3.2.11/redis.conf 9004
cp ~/redis-3.2.11/redis.conf 9005
cp ~/redis-3.2.11/redis.conf 9006
修改各 redis 实例的配置文件，以 9001 实例为例，bind 为本机 ip
daemonize yes
pidfile /usr/local/redis-cluster/9001/redis.pid
bind 192.168.1.6
port 9001
dir /usr/local/redis-cluster/9001/data
appendonly yes
cluster-enabled yes
cluster-config-file nodes-9001.conf
cluster-node-timeout 15000
9002-9006 实例配置同上，只是将其中的 9001 替换为相应的端口号。
启动实例
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9001/redis.conf
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9002/redis.conf
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9003/redis.conf
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9004/redis.conf
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9005/redis.conf
/usr/local/redis-cluster/bin/redis-server /usr/local/redis-cluster/9006/redis.conf
连接实例，确认各实例正常启动
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9001
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9002
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9003
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9004
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9005
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9006
安装 ruby 及 redis 依赖
apt-get install ruby
gem install redis
将单独的 redis 实例构建成集群（三主三从）
/usr/local/redis-cluster/bin/redis-trib.rb create --replicas 1 192.168.1.6:9001 192.168.1.6:9002 192.168.1.6:9003 192.168.1.6:9004 192.168.1.6:9005 192.168.1.6:9006
连接集群节点，注意比连接单实例时多了一个 -c 参数
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9001 -c
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9002 -c
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9003 -c
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9004 -c
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9005 -c
/usr/local/redis-cluster/bin/redis-cli -h 192.168.1.6 -p 9006 -c
查看集群信息
$ ./redis-cli -h 192.168.1.6 -p 9001 -c
192.168.1.6:9001> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_sent:55
cluster_stats_messages_received:50
192.168.1.6:9001> cluster nodes
e74db54eb4fa9dde324988e44bb3919129f944c8 192.168.1.6:9006 slave de0928f00ac377bf5b7806d088808f31804923eb 0 1522674425815 6 connected
186a18ae13203946253b537cfdab549b3be5282d 192.168.1.6:9005 slave 761269f61d3f95d3937b5b3451ea73f979aa40e6 0 1522674423811 5 connected
3e58b504f1419cf770313daf11f480bf48dd34a0 192.168.1.6:9001 myself,master - 0 0 1 connected 0-5460
6a1327d2385b0e270a9d1fa63bae3c14c879625e 192.168.1.6:9004 slave 3e58b504f1419cf770313daf11f480bf48dd34a0 0 1522674424813 4 connected
761269f61d3f95d3937b5b3451ea73f979aa40e6 192.168.1.6:9002 master - 0 1522674422809 2 connected 5461-10922
de0928f00ac377bf5b7806d088808f31804923eb 192.168.1.6:9003 master - 0 1522674426818 3 connected 10923-16383
客户端以 redis-cli 为例，数据读写测试脚本
$ ./redis-cli -h 192.168.1.6 -p 9001 -c
192.168.1.6:9001> set key1 value1
-> Redirected to slot [9189] located at 192.168.1.6:9002
OK
192.168.1.6:9002> get key1
"value1"
客户端以 jedis 为例，当前版本
<dependency>
<groupId>redis.clients</groupId>
<artifactId>jedis</artifactId>
<version>2.9.0</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
jedis 数据读写测试代码
Set<HostAndPort> jedisClusterNodes = new HashSet<HostAndPort>();
// Jedis Cluster will attempt to discover cluster nodes automatically
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9001));
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9002));
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9003));
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9004));
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9005));
jedisClusterNodes.add(new HostAndPort("192.168.1.6", 9006));
JedisCluster jc = new JedisCluster(jedisClusterNodes);
jc.set("key", "value");
String value = jc.get("key");
// jc.close();
从上面集群信息中可以看出，主从实例 9001 9004 分配的槽范围为 0-5460，主从实例 9002 9005 分配的槽范围为 5461-10922，主从实例 9003 9006 分配的槽范围为 10923-16383。
当用户通过客户端(redis-cli 或 jedis)向集群存入键值对时，数据存储的槽编号通过 key 计算出来，算法 CRC16(key) % 16384。
算法 CRC16(key) % 16384 的 java 代码实现
/**
* 计算键 key 要放入哪个槽
*
* @param key 键名
* @return slot 槽编号
*/
public static int slot(String key){
int slot = crc16(key) % 16384;
return slot;
}
/**
* 计算键 key 的 crc16 值
*
* @param key 键名
* @return crc16 值
* @see ~/redis-3.2.11/src/cluster.c and ~/redis-3.2.11/src/crc16.c
*/
public static int crc16(String key) {
int[] table = {
0x0000,0x1021,0x2042,0x3063,0x4084,0x50a5,0x60c6,0x70e7,
0x8108,0x9129,0xa14a,0xb16b,0xc18c,0xd1ad,0xe1ce,0xf1ef,
0x1231,0x0210,0x3273,0x2252,0x52b5,0x4294,0x72f7,0x62d6,
0x9339,0x8318,0xb37b,0xa35a,0xd3bd,0xc39c,0xf3ff,0xe3de,
0x2462,0x3443,0x0420,0x1401,0x64e6,0x74c7,0x44a4,0x5485,
0xa56a,0xb54b,0x8528,0x9509,0xe5ee,0xf5cf,0xc5ac,0xd58d,
0x3653,0x2672,0x1611,0x0630,0x76d7,0x66f6,0x5695,0x46b4,
0xb75b,0xa77a,0x9719,0x8738,0xf7df,0xe7fe,0xd79d,0xc7bc,
0x48c4,0x58e5,0x6886,0x78a7,0x0840,0x1861,0x2802,0x3823,
0xc9cc,0xd9ed,0xe98e,0xf9af,0x8948,0x9969,0xa90a,0xb92b,
0x5af5,0x4ad4,0x7ab7,0x6a96,0x1a71,0x0a50,0x3a33,0x2a12,
0xdbfd,0xcbdc,0xfbbf,0xeb9e,0x9b79,0x8b58,0xbb3b,0xab1a,
0x6ca6,0x7c87,0x4ce4,0x5cc5,0x2c22,0x3c03,0x0c60,0x1c41,
0xedae,0xfd8f,0xcdec,0xddcd,0xad2a,0xbd0b,0x8d68,0x9d49,
0x7e97,0x6eb6,0x5ed5,0x4ef4,0x3e13,0x2e32,0x1e51,0x0e70,
0xff9f,0xefbe,0xdfdd,0xcffc,0xbf1b,0xaf3a,0x9f59,0x8f78,
0x9188,0x81a9,0xb1ca,0xa1eb,0xd10c,0xc12d,0xf14e,0xe16f,
0x1080,0x00a1,0x30c2,0x20e3,0x5004,0x4025,0x7046,0x6067,
0x83b9,0x9398,0xa3fb,0xb3da,0xc33d,0xd31c,0xe37f,0xf35e,
0x02b1,0x1290,0x22f3,0x32d2,0x4235,0x5214,0x6277,0x7256,
0xb5ea,0xa5cb,0x95a8,0x8589,0xf56e,0xe54f,0xd52c,0xc50d,
0x34e2,0x24c3,0x14a0,0x0481,0x7466,0x6447,0x5424,0x4405,
0xa7db,0xb7fa,0x8799,0x97b8,0xe75f,0xf77e,0xc71d,0xd73c,
0x26d3,0x36f2,0x0691,0x16b0,0x6657,0x7676,0x4615,0x5634,
0xd94c,0xc96d,0xf90e,0xe92f,0x99c8,0x89e9,0xb98a,0xa9ab,
0x5844,0x4865,0x7806,0x6827,0x18c0,0x08e1,0x3882,0x28a3,
0xcb7d,0xdb5c,0xeb3f,0xfb1e,0x8bf9,0x9bd8,0xabbb,0xbb9a,
0x4a75,0x5a54,0x6a37,0x7a16,0x0af1,0x1ad0,0x2ab3,0x3a92,
0xfd2e,0xed0f,0xdd6c,0xcd4d,0xbdaa,0xad8b,0x9de8,0x8dc9,
0x7c26,0x6c07,0x5c64,0x4c45,0x3ca2,0x2c83,0x1ce0,0x0cc1,
0xef1f,0xff3e,0xcf5d,0xdf7c,0xaf9b,0xbfba,0x8fd9,0x9ff8,
0x6e17,0x7e36,0x4e55,0x5e74,0x2e93,0x3eb2,0x0ed1,0x1ef0
};
byte[] bytes = key.getBytes();
int crc = 0x0000;
for (byte b : bytes) {
crc = (crc << 8) ^ table[((crc >> 8) ^ b) & 0x00FF];
}
crc = crc & 0x3FFF;
return crc;
}
public static void main(String[] args) {
String key = "key1";
int slot = slot(key);
System.out.print("slot=" + slot); // 输出 slot=9189
}
cd /elasticsearch/elasticsearch-2.3.2/bin && su elasticsearch && ./elasticsearch -d
好像执行./elasticsearch -d时，还是在root用户
根据他说的情况，我想到 su 是有命令参数的，根据他的命令，我修改了一下
su - elasticsearch -c "cd /elasticsearch/elasticsearch-2.3.2/bin && ./elasticsearch -d"
发给他后，他在自己的环境执行后，结果确实成功了。
bundle exec jekyll server
报以下错误
Dependency Error: Yikes! It looks like you don’t have jekyll-remote-theme or one of its dependencies installed. In order to use Jekyll as currently configured, you’ll need to install this gem. The full error message from Ruby is: ‘Could not open library ‘libcurl’: �Ҳ���ָ����ģ�顣 . Could not open library ‘libcurl.dll’: �Ҳ���ָ����ģ�顣 . Could not open library ‘libcurl.so.4’: �Ҳ���ָ����ģ�顣 . Could not open library ‘libcurl.so.4.dll’: �Ҳ���ָ����ģ�顣 ‘ If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!
经网上查询并亲自试验，发现有两种方法解决这个问题。
修改前内容
source 'https://rubygems.org'
gem 'github-pages', group: :jekyll_plugins
#gem 'jekyll-admin', group: :jekyll_plugins
修改后内容
source 'https://rubygems.org'
gem 'github-pages'
#gem 'jekyll-admin', group: :jekyll_plugins
在 plugins 下添加 jekyll-paginate，修改前内容
plugins:
# jemoji conficts with toc in some no-ascii post
# - jemoji
- jekyll-sitemap
- jekyll-feed
修改后内容
plugins:
# jemoji conficts with toc in some no-ascii post
# - jemoji
- jekyll-sitemap
- jekyll-feed
- jekyll-paginate
可以直接从网上下载 libcurl.dll 放到系统 path 下，或者下载 curl 源码自己编译。
打开网页 https://curl.haxx.se/gknw.net/7.40.0/dist-w64/，并选择一个包下载，如 curl-7.40.0-ssh2-ssl-sspi-zlib-static-bin-w64.zip，解压后将目录中的 libcurl.dll 放到系统 path 下，如 Ruby 安装目录 bin 中。
打开网页 https://curl.haxx.se/download.html，并选择一个源码包下载，如 curl-7.57.0.zip，解压包到 C:\curl-7.57.0，在终端（CMD 或 Powershell）下，切换到本机 DevKit 目录，运行 msys.bat，此时会弹出一个 mingw 环境窗口，在 mingw 环境窗口中输入命令 cd /c/curl-7.57.0/lib 进入到 C:\curl-7.57.0\lib 目录，然后执行 make -f Makefile.m32 编译源码，编译完成后会在 lib 目录下会生成 libcurl.dll，将 libcurl.dll 放到系统 path 下，如 Ruby 安装目录 bin 中。
可以比较快速地进入本地调试步骤，而不用修改操作系统。
如果远方仓库（如 github）中 Gemfile 和 _config.yml plugins 部分保持主题默认的话，本地调试完成后提交时有可能误将这两部分误提交。
操作系统安装 libcurl.dll 后，本地 Gemfile 和 _config.yml plugins 部分可以与远方仓库（如 github）保持一致，不用做任何修改。
要修改操作系统，比较麻烦，还有可能给系统带来安全性的问题。
java org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for connection from pool
解决方法，修改连接池配置，增大连接数
RequestConfig config = RequestConfig.custom()
.setSocketTimeout(socketTimeout)
.setConnectTimeout(connectTimeout)
.setConnectionRequestTimeout(connectionRequestTimeout).build();
httpClient = HttpClients.custom().setDefaultRequestConfig(config)
.setMaxConnTotal(maxConnTotal)
.setMaxConnPerRoute(maxConnPerRoute).build();