[SSL]证书提供商
免费starsslwosign收费https://www.gogetssl.com/https://cheapsslsecurity.com/https://www.ssl2buy.com/ssl-discount-offers/更新:現在 wosign 和 startssl 都不能推薦了。
免费starsslwosign收费https://www.gogetssl.com/https://cheapsslsecurity.com/https://www.ssl2buy.com/ssl-discount-offers/更新:現在 wosign 和 startssl 都不能推薦了。
net.ipv4.ip_forward = 1net.ipv4.conf.all.send_redirects = 0net.core.rmem_max = 16777216net.core.wmem_max = 16777216net.ipv4.tcp_rmem = 4096 87380 16777216net.ipv4.tcp_wmem = 4096 65536 16777216net.core.netdev_max_backlog = 30000net.ipv4.ip_forward = 1net.ipv6.conf.all.disable_ipv6 = 1net.ipv6.conf.default.disable_ipv6 = 1net.ipv6.conf.lo.disable_ipv6 = 1net.ipv4.tcp_timestamps = 0net.ipv4.tcp_sack = 1net.ipv4.tcp_window_scaling = 1net.ipv4.tcp_fastopen = 1
Virtualbox 不直接支持USB启动,需要经过一道转换:1. 创建USB映射:sudo VBoxManage internalcommands createrawvmdk -filename usb.vmdk -rawdisk /dev/sdc替换/dev/sdc为需要的USB设备启动项目2. 确认自己用户在disk组(即是/dev/sdc拥有组)sudo gpasswd -a scys disk3. 加载第一步创建的usb.vmdk到vbox虚拟机中,启动就OK。
nginx: include next config:# smokping nginx configuare# system os: debian 7.0location /smokeping { access_log /var/log/nginx/server.smokeping.access.log; error_log /var/log/nginx/server.smokeping.error.log; root /var/www; index smokeping.cgi; auth_basic “Restricted”; auth_basic_user_file /var/www/users.htpasswd; location ~ .cgi$ { root /var/www; include /etc/nginx/fastcgi_params; fastcgi_pass unix:/var/run/fcgiwrap.socket; fastcgi_index smokeping.cgi; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; }}new folder:mkdir /var/www/smokepinglink file to /var/www/smokeping:ln -s /usr/share/smokeping/www/* /var/www/smokeping/create htpasswd filehtpasswod /var/www/users.htpasswdreload the sevice configureservice nginx reload
http://serverfault.com/questions/525923/lsi-3ware-tw-cli-and-tdm2-segfault-with-debian-linux-kernels-after-3-8?answertab=votes#tab-topThe problem isn’t the date, it’s that tw_cli is looking for X.Y.Z(-R-arch) in the release and it’s only getting X.Y(-R-arch) - 3.2.0-4-amd64 vs 3.10-2-amd64. When the release is set to 3.10.0-2-amd64 it runs fine. They may be doing a sscanf() with limited formats, and little or no error checking.jam:~# uname -r3.10-2-amd64jam:~# tw_cli /c0 show firmwareSegmentation faultjam:~# echo 3.10.0-2-amd64 > /sys/module/utsname/parameters/releasejam:~# uname -r3.10.0-2-amd64jam:~# tw_cli /c0 show firmware/c0 Firmware Version = FE9X 4....