安裝環境
Distributor ID: Debian
Description: Debian GNU/Linux 7.11 (wheezy)
Release: 7.11
Codename: wheezy
本文默認軟件包存放位置
/home/yx/src/
本文默認軟件包安裝位置
/home/yx/server
本文默認軟件包解壓位置
/tmp/
根據本次要搭建的環境，需要做系統優化
- 更新源
cat <<eof> /etc/apt/sources.list
deb http://mirrors.163.com/debian wheezy main non-free contrib
deb http://mirrors.163.com/debian wheezy-proposed-updates main contrib non-free
deb-src http://mirrors.163.com/debian wheezy main non-free contrib
deb-src http://mirrors.163.com/debian wheezy-proposed-updates main contrib non-free
deb http://mirrors.163.com/debian-security wheezy/updates main contrib non-free
deb-src http://mirrors.163.com/debian-security wheezy/updates main contrib non-free
eof
apt-get update
apt-get install sudo vim unzip lrzsz rsync subversion zip git
- vim /etc/security/limits.conf
* soft nproc 102400
* hard nproc 102400
* soft nofile 300000
* hard nofile 300000
- 更改crontab默認編輯器爲vim
update-alternatives --config editor
- 修改所有 linux 用戶的環境變量文件， 每個進程可以同時打開的最大文件數
vim /etc/profile
ulimit -n 300000 //增加
- 優化Linux內核sysctl.conf參數來提高服務器併發處理能力
- 參考鏈接：https://blog.csdn.net/hj7jay/article/details/52093102
vim /etc/sysctl.conf
net.ipv4.tcp_max_tw_buckets = 800000
net.ipv4.tcp_sack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 16384 16777216
net.ipv4.tcp_syncookies = 1
net.core.wmem_default = 8388608
net.core.rmem_default = 8388608
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.netdev_max_backlog = 800000
net.core.somaxconn = 65535
net.ipv4.tcp_max_orphans = 3276800
net.ipv4.tcp_max_syn_backlog = 262144
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_synack_retries = 1
net.ipv4.tcp_syn_retries = 1
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_mem = 94500000 915000000 927000000
net.ipv4.tcp_fin_timeout = 1
net.ipv4.tcp_keepalive_time = 30
net.ipv4.ip_forward = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.shmmax = 134217728
kernel.sysrq = 0
kernel.core_uses_pid = 1
kernel.msgmni = 1000
kernel.msgmax = 81920
kernel.msgmnb = 163840
kernel.shmmax = 4294967295
kernel.shmall = 268435456
kernel.sem = 250 32000 100 128
fs.file-max = 1645037
vm.max_map_count=655360
vm.swappiness = 0
sysctl -p //使配置生效
- 更改普通用戶權限
vim /etc/sudoers
yx ALL=(ALL:ALL) ALL
yx ALL=NOPASSWD: /usr/sbin/ntpdate
yx ALL=NOPASSWD: /bin/date
- 配置自動補全
vim .bashrc
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
. /etc/bash_completion
fi
source .bashrc
- 忽略大小寫
set completion-ignore-case on
開始編譯安裝服務
- 安裝依賴庫（C編譯器）
sudo apt-get install build-essential -y
-
安裝pcre正則表達式庫
tar zxf src/pcre-8.38.tar.gz -C /tmp/
cd /tmp/pcre-8.38/
./configure --enable-utf8 --enable-jit
make
sudo make install
pcre-config --version
8.38
-
安裝依賴庫OPENSSL
sudo apt-get install libcurl4-openssl-dev -y
-
安裝Nginx
mkdir -p {/home/yx/server/nginx/conf,/home/yx/server/nginx/var/log,/home/yx/server/nginx/var/run,/home/yx/server/nginx/logs} //創建目錄
tar zxf src/nginx-1.11.2.tar.gz -C /tmp/
cd /tmp/nginx-1.11.2/
./configure --prefix=/home/yx/server/nginx \
--conf-path=/home/yx/server/nginx/conf/nginx.conf \
--error-log-path=/home/yx/server/nginx/var/log/error.log \
--pid-path=/home/yx/server/nginx/var/run/nginx.pid \
--lock-path=/home/yx/server/nginx/var/run/nginx.lock \
--with-http_ssl_module \
--with-http_stub_status_module \
--with-http_gzip_static_module \
--with-http_sub_module \
--with-http_flv_module \
--with-http_mp4_module \
--with-http_random_index_module \
--with-http_dav_module \
--with-http_realip_module
make
make install
- 配置項
sudo chown root /home/yx/server/nginx/sbin/nginx //更改屬組爲root
sudo chmod u+s /home/yx/server/nginx/sbin/nginx //賦予u+s權限
sudo ln -s /home/yx/server/nginx/sbin/nginx /usr/local/bin/ //軟連接
-
安裝依賴庫LIBTDL
sudo apt-get install libltdl-dev -y
-
安裝ImageMagick
tar zxf src/ImageMagick.tar.gz -C /tmp/
cd /tmp/ImageMagick-6.9.3-7/
./configure --prefix=/home/yx/server/ImageMagick/ --enable-lzw --with-modules --with-quantum-depth=8 --enable-shared --disable-openmp
make
make install
sudo ln -s /home/yx/server/ImageMagick/bin/convert /usr/bin/ //全局
-
安裝php依賴庫
mkdir /home/yx/server/php/log -p
sudo apt-get install libxml2-dev libbz2-dev libjpeg8-dev libpng12-dev libmcrypt-dev autoconf libmemcached-dev libgearman-dev -y
tar zxf src/php-5.4.22.tar.gz -C /tmp/
cd /tmp/php-5.4.22/
unzip /home/yx/src/freetype-2.4.11.zip //安裝freetype庫
cd freetype-2.4.11/
./configure && make
sudo make install
-
編譯安裝PHP5.4
cd /tmp/php-5.4.22/
./configure --prefix=/home/yx/server/php \
--enable-cli \
--with-libxml-dir=/usr \
--with-kerberos=/usr \
--enable-bcmath \
--enable-calendar \
--enable-fpm \
--with-mcrypt \
--enable-soap \
--enable-exif \
--enable-mbstring \
--enable-pdo \
--with-pdo-mysql=mysqlnd \
--with-mysql-sock \
--with-curl=/usr \
--enable-ftp \
--enable-mbstring \
--with-png-dir \
--with-gd \
--enable-gd-native-ttf \
--with-freetype-dir=/usr/ \
--disable-debug \
--disable-rpath \
--enable-inline-optimization \
--with-bz2 \
--with-zlib=/usr \
--enable-sockets \
--enable-sysvsem \
--enable-sysvshm \
--enable-pcntl \
--enable-mbregex \
--with-mhash \
--enable-zip \
--with-pcre-regex \
--with-mysql=mysqlnd \
--with-mysqli=mysqlnd \
--with-gd \
--with-jpeg-dir \
--with-openssl
make
make install
cp /tmp/php-5.4.22/php.ini-development /home/yx/server/php/lib/php.ini
cp /home/yx/server/php/etc/php-fpm.conf.default /home/yx/server/php/etc/php-fpm.conf
- 安裝PHP擴展，此處約定所有擴展解壓目錄爲
/tmp/php-5.4.22
- yaf擴展
unzip /home/yx/src/yaf.zip -d /tmp/php-5.4.22 //此處解壓在PHP解壓目錄
cd php-yaf-master/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- ssh2擴展
sudo apt-get install libssh2-1-dev -y （Ubuntu需要）
wget http://pecl.php.net/get/ssh2-0.13.tgz
tar zxf /home/yx/src/ssh2-0.13.tgz -C /tmp/
cd /tmp/ssh2-0.13/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install //此處需要重啓Nginx&PHP
- bcmath擴展(PHP5.6自帶)
cd /tmp/php-5.4.22/ext/bcmath/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- yar 擴展
tar zxf /home/yx/src/yar-1.2.5.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/yar-1.2.5/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- memcached擴展
tar zxf /home/yx/src/memcached-2.1.0.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/memcached-2.1.0/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- memcache擴展
tar zxf /home/yx/src/memcache-2.2.7.tgz -C /tmp/
cd /tmp/memcache-2.2.7/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- redis擴展
tar zxf /home/yx/src/redis-php-2.2.4.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/redis-2.2.4
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- gearman擴展
tar zxf /home/yx/src/gearman-1.1.0.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/gearman-1.1.0/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- msgpack擴展
tar zxf /home/yx/src/msgpack-0.5.7.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/msgpack-0.5.7/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- zendopcache擴展
tar zxf /home/yx/src/zendopcache-7.0.2.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/zendopcache-7.0.2/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- imagick擴展
tar zxf src/imagick-3.4.3.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/imagick-3.4.3/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config --with-imagick=/home/yx/server/ImageMagick/
make && make install
- OpenSSL擴展
cd /tmp/php-5.4.22/ext/openssl/
cp config0.m4 config.m4
/home/yx/server/php/bin/phpize
./configure --with-openssl --with-php-config=/home/yx/server/php/bin/php-config
make && make install
openssl version //查看OpenSSL是否安裝
OpenSSL 1.0.1t 3 May 2016 //版本
- Swool擴展
tar zxf src/swoole-1.9.16.tgz -C /tmp/php-5.4.22/
cd /tmp/php-5.4.22/swoole-1.9.16/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make && make install
- connect_pool擴展
unzip /home/yx/src/php-cp-master.zip -d /tmp/php-5.4.22/
cd /tmp/php-5.4.22/php-cp-master/
/home/yx/server/php/bin/phpize
./configure --with-php-config=/home/yx/server/php/bin/php-config
make
sudo make install
配置
mkdir -p {/home/yx/server/php-cp/etc/,/home/yx/server/php-cp/sbin,/home/yx/server/php-cp/logs}
cp /tmp/php-5.4.22/php-cp-master/config.ini.example /home/yx/server/php-cp/etc/pool.ini
cd /tmp/php-5.4.22/php-cp-master/
[ -f /bin/env ] || sudo ln -s /usr/bin/env /bin/env //當前目錄爲pool解壓目錄
sudo cp ./pool_server /home/yx/server/php-cp/sbin/
sudo chmod +x /home/yx/server/php-cp/sbin/pool_server
sudo ln -s /home/yx/server/php/bin/php /usr/local/bin/
sudo ln -s /home/yx/server/php-cp/sbin/pool_server /usr/local/bin/
sed -i "s/log_file.*/log_file\ =\ \/home\/yx\/server\/php-cp\/logs\/php_cp_server.log/g" /home/yx/server/php-cp/etc/pool.ini //更改日誌存放目錄
vim /home/yx/server/php-cp/sbin/pool_server //更改默認讀取配置文件目錄
$config_file = "/home/yx/server/php-cp/etc/pool.ini"; //pool_server的配置文件
sudo pool_server start //必須將本擴展加入php.ini配置文件方可啓動
sudo pool_server status
PHP文件註釋方法爲（;）
- 在php.ini文件中添加剛纔安裝的擴展
vim server/php/lib/php.ini //插入擴展配置模塊
;extension=connect_pool.so
extension=gearman.so
extension=imagick.so
extension=memcached.so
extension=memcache.so
extension=msgpack.so
;extension=opcache.so
;extension=openssl.so
extension=redis.so
extension=ssh2.so
extension=swoole.so
extension=yaf.so
extension=yar.so
;extension=bcmath.so
此處有可能不全，另外【;】號爲註釋符
-
安裝MySQL
mkdir -p {/home/yx/server/mysql/data,/home/yx/server/mysql/etc,/home/yx/server/mysql/var/run,/home/yx/server/mysql/mysqllog/binlog,/home/yx/server/mysql/mysqllog/relay/relay-bin}
sudo apt-get install cmake libncurses5-dev build-essential //安裝依賴
- 編譯安裝
tar zxf src/mysql-boost-5.7.12.tar.gz -C /tmp/
cp src/boost_1_59_0.tar.gz /tmp/mysql-5.7.12/
cd /tmp/mysql-5.7.12/
cmake -DCMAKE_INSTALL_PREFIX=/home/yx/server/mysql \
-DMYSQL_DATADIR=/home/yx/server/mysql/data \
-DSYSCONFDIR=/home/yx/server/mysql/etc \
-DDOWNLOAD_BOOST=1 \
-DWITH_BOOST=/tmp/mysql-5.7.12/boost_1_59_0.tar.gz \
-DMYSQL_USER=yx \
-DWITH_MYISAM_STORAGE_ENGINE=1 \
-DWITH_INNOBASE_STORAGE_ENGINE=1 \
-DWITH_ARCHIVE_STORAGE_ENGINE=1 \
-DWITH_MEMORY_STORAGE_ENGINE=1 \
-DWITH_READLINE=1 \
-DMYSQL_UNIX_ADDR=/home/yx/server/mysql/var/mysqld.sock \
-DMYSQL_TCP_PORT=3357 \
-DENABLED_LOCAL_INFILE=1 \
-DENABLE_DOWNLOADS=1 \
-DWITH_PARTITION_STORAGE_ENGINE=1 \
-DEXTRA_CHARSETS=all \
-DDEFAULT_CHARSET=utf8 \
-DDEFAULT_COLLATION=utf8_general_ci \
-DWITH_DEBUG=0 \
-DMYSQL_MAINTAINER_MODE=0 \
-DWITH_SSL:STRING=bundled \
-DWITH_ZLIB:STRING=bundled
make && make install
- 配置
/home/yx/server/mysql/bin/mysqld --initialize-insecure --user=yx --basedir=/home/yx/server/mysql --datadir=/home/yx/server/mysql/data //初始化數據庫
sudo cp /home/yx/server/mysql/support-files/mysql.server /etc/init.d/mysqld
cp /usr/local/mysql/support-files/my-default.cnf /home/yx/server/mysql/etc/my.cnf
sudo ln -s /home/yx/server/mysql/bin/mysql /usr/local/bin/
sudo ln -s /home/yx/server/mysql/bin/mysqldump /usr/local/bin/
sudo ln -s /home/yx/server/mysql/bin/mysqladmin /usr/local/bin/
sudo mkdir /var/run/mysqld/
sudo chmod 777 /var/run/mysqld/
echo "skip-grant-tables=1" >> /home/yx/server/mysql/etc/my.cnf //設置空密碼登錄
/etc/init.d/mysqld start
mysql -u root -p //驗證空密碼可以正常登錄
UPDATE mysql.user SET authentication_string=password('123456') WHERE user='root';
flush privileges; //更改當前用戶密碼並使之生效
sed -i '$d' server/mysql/etc/my.cnf //刪除掉剛添加的skip--
驗證設置的密碼是否可以成功登錄，然後創建次級用戶wdty
GRANT ALL ON *.* to 'test'@'%' identified by '123456';
-
安裝redis
mkdir -p {/home/yx/server/redis/etc/,/home/yx/server/redis/logs/,/home/yx/server/redis/datafile/}
tar zxf src/redis-3.2.8.tar.gz -C /tmp/
cd /tmp/redis-3.2.8
make install PREFIX=/home/yx/server/redis/
vim /home/yx/server/redis/etc/redis.conf //拷貝配置文件到該目錄下
附鏈接一份：http://d2bc7aa4.wiz03.com/share/s/3iL7GA0kvksQ259jUa3bo_D51iuQTs3kK4mB2U9cHF2QB17F
/home/yx/server/redis/bin/redis-server /home/yx/server/redis/etc/redis.conf //啓動服務
- 配置項
# Redis configuration file example
# Note on units: when memory size is needed, it is possible to specify
# it in the usual form of 1k 5GB 4M and so forth:
#
# 1k => 1000 bytes
# 1kb => 1024 bytes
# 1m => 1000000 bytes
# 1mb => 1024*1024 bytes
# 1g => 1000000000 bytes
# 1gb => 1024*1024*1024 bytes
#
# units are case insensitive so 1GB 1Gb 1gB are all the same.
# By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize yes
# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
# default. You can specify a custom pid file location here.
pidfile /var/run/redis.pid
# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
port 16379
# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for incoming connections.
#
# bind 127.0.0.1
# Specify the path for the unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /tmp/redis.sock
# unixsocketperm 755
# Close the connection after a client is idle for N seconds (0 to disable)
timeout 0
# TCP keepalive.
#
# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
# of communication. This is useful for two reasons:
#
# 1) Detect dead peers.
# 2) Take the connection alive from the point of view of network
# equipment in the middle.
#
# On Linux, the specified value (in seconds) is the period used to send ACKs.
# Note that to close the connection the double of the time is needed.
# On other kernels the period depends on the kernel configuration.
#
# A reasonable value for this option is 60 seconds.
tcp-keepalive 0
# Specify the server verbosity level.
# This can be one of:
# debug (a lot of information, useful for development/testing)
# verbose (many rarely useful info, but not a mess like the debug level)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel notice
# Specify the log file name. Also 'stdout' can be used to force
# Redis to log on the standard output. Note that if you use standard
# output for logging but daemonize, logs will be sent to /dev/null
logfile "/home/yx/server/redis/logs/redis.log"
# To enable logging to the system logger, just set 'syslog-enabled' to yes,
# and optionally update the other syslog parameters to suit your needs.
# syslog-enabled no
# Specify the syslog identity.
# syslog-ident redis
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
# syslog-facility local0
# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and 'databases'-1
databases 16
################################ SNAPSHOTTING #################################
#
# Save the DB on disk:
#
# save <seconds> <changes>
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
#
# Note: you can disable saving at all commenting all the "save" lines.
#
# It is also possible to remove all the previously configured save
# points by adding a save directive with a single empty string argument
# like in the following example:
#
# save ""
save 900 1
save 300 10
save 60 10000
# By default Redis will stop accepting writes if RDB snapshots are enabled
# (at least one save point) and the latest background save failed.
# This will make the user aware (in an hard way) that data is not persisting
# on disk properly, otherwise chances are that no one will notice and some
# distater will happen.
#
# If the background saving process will start working again Redis will
# automatically allow writes again.
#
# However if you have setup your proper monitoring of the Redis server
# and persistence, you may want to disable this feature so that Redis will
# continue to work as usually even if there are problems with disk,
# permissions, and so forth.
stop-writes-on-bgsave-error yes
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
# This makes the format more resistant to corruption but there is a performance
# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
# for maximum performances.
#
# RDB files created with checksum disabled have a checksum of zero that will
# tell the loading code to skip the check.
rdbchecksum yes
# The filename where to dump the DB
dbfilename dump.rdb
# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
dir /home/yx/server/redis/datafile/
################################# REPLICATION #################################
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# slaveof <masterip> <masterport>
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth <master-password>
# When a slave loses its connection with the master, or when the replication
# is still in progress, the slave can act in two different ways:
#
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
# still reply to client requests, possibly with out of date data, or the
# data set may just be empty if this is the first synchronization.
#
# 2) if slave-serve-stale-data is set to 'no' the slave will reply with
# an error "SYNC with master in progress" to all the kind of commands
# but to INFO and SLAVEOF.
#
slave-serve-stale-data yes
# You can configure a slave instance to accept writes or not. Writing against
# a slave instance may be useful to store some ephemeral data (because data
# written on a slave will be easily deleted after resync with the master) but
# may also cause problems if clients are writing to it because of a
# misconfiguration.
#
# Since Redis 2.6 by default slaves are read-only.
#
# Note: read only slaves are not designed to be exposed to untrusted clients
# on the internet. It's just a protection layer against misuse of the instance.
# Still a read only slave exports by default all the administrative commands
# such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
# security of read only slaves using 'rename-command' to shadow all the
# administrative / dangerous commands.
slave-read-only yes
# Slaves send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_slave_period option. The default value is 10
# seconds.
#
# repl-ping-slave-period 10
# The following option sets a timeout for both Bulk transfer I/O timeout and
# master data or ping response timeout. The default value is 60 seconds.
#
# It is important to make sure that this value is greater than the value
# specified for repl-ping-slave-period otherwise a timeout will be detected
# every time there is low traffic between the master and the slave.
#
# repl-timeout 60
# Disable TCP_NODELAY on the slave socket after SYNC?
#
# If you select "yes" Redis will use a smaller number of TCP packets and
# less bandwidth to send data to slaves. But this can add a delay for
# the data to appear on the slave side, up to 40 milliseconds with
# Linux kernels using a default configuration.
#
# If you select "no" the delay for data to appear on the slave side will
# be reduced but more bandwidth will be used for replication.
#
# By default we optimize for low latency, but in very high traffic conditions
# or when the master and slaves are many hops away, turning this to "yes" may
# be a good idea.
repl-disable-tcp-nodelay no
# The slave priority is an integer number published by Redis in the INFO output.
# It is used by Redis Sentinel in order to select a slave to promote into a
# master if the master is no longer working correctly.
#
# A slave with a low priority number is considered better for promotion, so
# for instance if there are three slaves with priority 10, 100, 25 Sentinel will
# pick the one wtih priority 10, that is the lowest.
#
# However a special priority of 0 marks the slave as not able to perform the
# role of master, so a slave with priority of 0 will never be selected by
# Redis Sentinel for promotion.
#
# By default the priority is 100.
slave-priority 100
################################## SECURITY ###################################
# Require clients to issue AUTH <PASSWORD> before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# requirepass foobared
# Command renaming.
#
# It is possible to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# hard to guess so that it will still be available for internal-use tools
# but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possible to completely kill a command by renaming it into
# an empty string:
#
# rename-command CONFIG ""
#
# Please note that changing the name of commands that are logged into the
# AOF file or transmitted to slaves may cause problems.
################################### LIMITS ####################################
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 10000
# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys
# accordingly to the eviction policy selected (see maxmemmory-policy).
#
# If Redis can't remove keys according to the policy, or if the policy is
# set to 'noeviction', Redis will start to reply with errors to commands
# that would use more memory, like SET, LPUSH, and so on, and will continue
# to reply to read-only commands like GET.
#
# This option is usually useful when using Redis as an LRU cache, or to set
# an hard memory limit for an instance (using the 'noeviction' policy).
#
# WARNING: If you have slaves attached to an instance with maxmemory on,
# the size of the output buffers needed to feed the slaves are subtracted
# from the used memory count, so that network problems / resyncs will
# not trigger a loop where keys are evicted, and in turn the output
# buffer of slaves is full with DELs of keys evicted triggering the deletion
# of more keys, and so forth until the database is completely emptied.
#
# In short... if you have slaves attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for slave
# output buffers (but this is not needed if the policy is 'noeviction').
#
# maxmemory <bytes>
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached. You can select among five behaviors:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys-random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
#
# Note: with any of the above policies, Redis will return an error on write
# operations, when there are not suitable keys for eviction.
#
# At the date of writing this commands are: set setnx setex append
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
# getset mset msetnx exec sort
#
# The default is:
#
# maxmemory-policy volatile-lru
# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can select as well the sample
# size to check. For instance for default Redis will check three keys and
# pick the one that was used less recently, you can change the sample size
# using the following configuration directive.
#
# maxmemory-samples 3
############################## APPEND ONLY MODE ###############################
# By default Redis asynchronously dumps the dataset on disk. This mode is
# good enough in many applications, but an issue with the Redis process or
# a power outage may result into a few minutes of writes lost (depending on
# the configured save points).
#
# The Append Only File is an alternative persistence mode that provides
# much better durability. For instance using the default data fsync policy
# (see later in the config file) Redis can lose just one second of writes in a
# dramatic event like a server power outage, or a single write if something
# wrong with the Redis process itself happens, but the operating system is
# still running correctly.
#
# AOF and RDB persistence can be enabled at the same time without problems.
# If the AOF is enabled on startup Redis will load the AOF, that is the file
# with the better durability guarantees.
#
# Please check http://redis.io/topics/persistence for more information.
appendonly no
# The name of the append only file (default: "appendonly.aof")
# appendfilename appendonly.aof
# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only one time every second. Compromise.
#
# The default is "everysec", as that's usually the right compromise between
# speed and data safety. It's up to you to understand if you can relax this to
# "no" that will let the operating system flush the output buffer when
# it wants, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting),
# or on the contrary, use "always" that's very slow but a bit safer than
# everysec.
#
# More details please check the following article:
# http://antirez.com/post/redis-persistence-demystified.html
#
# If unsure, use "everysec".
# appendfsync always
appendfsync everysec
# appendfsync no
# When the AOF fsync policy is set to always or everysec, and a background
# saving process (a background save or AOF log background rewriting) is
# performing a lot of I/O against the disk, in some Linux configurations
# Redis may block too long on the fsync() call. Note that there is no fix for
# this currently, as even performing fsync in a different thread will block
# our synchronous write(2) call.
#
# In order to mitigate this problem it's possible to use the following option
# that will prevent fsync() from being called in the main process while a
# BGSAVE or BGREWRITEAOF is in progress.
#
# This means that while another child is saving, the durability of Redis is
# the same as "appendfsync none". In practical terms, this means that it is
# possible to lose up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
#
# If you have latency problems turn this to "yes". Otherwise leave it as
# "no" that is the safest pick from the point of view of durability.
no-appendfsync-on-rewrite no
# Automatic rewrite of the append only file.
# Redis is able to automatically rewrite the log file implicitly calling
# BGREWRITEAOF when the AOF log size grows by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the
# latest rewrite (if no rewrite has happened since the restart, the size of
# the AOF at startup is used).
#
# This base size is compared to the current size. If the current size is
# bigger than the specified percentage, the rewrite is triggered. Also
# you need to specify a minimal size for the AOF file to be rewritten, this
# is useful to avoid rewriting the AOF file even if the percentage increase
# is reached but it is still pretty small.
#
# Specify a percentage of zero in order to disable the automatic AOF
# rewrite feature.
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
################################ LUA SCRIPTING ###############################
# Max execution time of a Lua script in milliseconds.
#
# If the maximum execution time is reached Redis will log that a script is
# still in execution after the maximum allowed time and will start to
# reply to queries with an error.
#
# When a long running script exceed the maximum execution time only the
# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
# used to stop a script that did not yet called write commands. The second
# is the only way to shut down the server in the case a write commands was
# already issue by the script but the user don't want to wait for the natural
# termination of the script.
#
# Set it to 0 or a negative value for unlimited execution without warnings.
lua-time-limit 5000
################################## SLOW LOG ###################################
# The Redis Slow Log is a system to log queries that exceeded a specified
# execution time. The execution time does not include the I/O operations
# like talking with the client, sending the reply and so forth,
# but just the time needed to actually execute the command (this is the only
# stage of command execution where the thread is blocked and can not serve
# other requests in the meantime).
#
# You can configure the slow log with two parameters: one tells Redis
# what is the execution time, in microseconds, to exceed in order for the
# command to get logged, and the other parameter is the length of the
# slow log. When a new command is logged the oldest one is removed from the
# queue of logged commands.
# The following time is expressed in microseconds, so 1000000 is equivalent
# to one second. Note that a negative number disables the slow log, while
# a value of zero forces the logging of every command.
slowlog-log-slower-than 10000
# There is no limit to this length. Just be aware that it will consume memory.
# You can reclaim memory used by the slow log with SLOWLOG RESET.
slowlog-max-len 128
############################### ADVANCED CONFIG ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
# Similarly to hashes, small lists are also encoded in a special way in order
# to save a lot of space. The special representation is only used when
# you are under the following limits:
list-max-ziplist-entries 512
list-max-ziplist-value 64
# Sets have a special encoding in just one case: when a set is composed
# of just strings that happens to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
set-max-intset-entries 512
# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation Redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into an hash table
# that is rehashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# active rehashing the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply form time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients
# slave -> slave clients and MONITOR clients
# pubsub -> clients subcribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and slave clients, since
# subscribers and slaves receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeot, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are perforemd with the same frequency, but Redis checks for
# tasks to perform accordingly to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
hz 10
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof-rewrite-incremental-fsync yes
################################## INCLUDES ###################################
# Include one or more other config files here. This is useful if you
# have a standard template that goes to all Redis server but also need
# to customize a few per-server settings. Include files can include
# other files, so use this wisely.
#
# include /path/to/local.conf
# include /path/to/other.conf
protected-mode no
sudo ln -s /home/yx/server/redis/bin/redis-server /usr/local/bin/
sudo ln -s /home/yx/server/redis/bin/redis-cli /usr/local/bin/
logfile "/home/yx/server/redis/logs/redis.log" //設置日誌存放目錄
dir /home/yx/server/redis/datafile/ //設置緩存目錄
-
安裝gearmand
sudo apt-get install libboost-dev libboost-all-dev gperf -y
wget http://nchc.dl.sourceforge.net/project/libuuid/libuuid-1.0.3.tar.gz -P /home/yx/src/
tar zxf src/gearmand-1.1.12.tar.gz -C /tmp/
tar zxf /home/yx/src/libuuid-1.0.3.tar.gz -C /tmp/gearmand-1.1.12/
cd /tmp/gearmand-1.1.12/libuuid-1.0.3/
./configure
sudo make
sudo make install
mkdir -p /home/yx/server/gearmand/var/log
cd /tmp/gearmand-1.1.12/
./configure --prefix=/home/yx/server/gearmand/
make && make install
sudo chown root /home/yx/server/gearmand/sbin/gearmand
sudo chmod u+s /home/yx/server/gearmand/sbin/gearmand
/home/yx/server/gearmand/sbin/gearmand --user=yx --listen=0.0.0.0 -d
-
安裝memcached
mkdir -p /home/yx/server/memcached/var/
tar zxf src/memcached-1.4.34.tar.gz -C /tmp/
cd /tmp/memcached-1.4.34/
./configure --prefix=/home/yx/server/memcached/
make
make install
/home/yx/server/memcached/bin/memcached -d -m 4096 -l 0.0.0.0 -p 12306 -u yx -c 4096 -P /home/yx/server/memcached/var/memcached.pid //啓動服務
- 到此安裝結束，有問題請評論~~