将windows 八安装到移动硬盘中 ...- Redis windows 测试redis持久化效...- 中国电信牛逼，广告放在浏览器上解决方法

当前位置: 操作系统/服务器>windows

本页文章导读:

▪将windows 八安装到移动硬盘中将windows 8安装到移动硬盘中安装之前将该移动硬盘的该分区设置为主分区并为活动，安装后，进BIOS更改启动项，从移动硬盘启动即可。注意：WIN$Man这个工具在下面的第一张图片中（将.........

▪ Redis windows 测试redis持久化效能 Redis windows 测试redis持久化功能下载地址：servicestack.googlecode.com/files/redis-2.0.2.zip 下载完之后解压到你磁盘上的，我的是F:\redis-2.0.2 还需要在redis根目录增加一个redis的配置文件redis.conf，文件.........

▪ 中国电信牛逼，广告放在浏览器上解决方法中国电信牛逼，广告放在浏览器上几个月前偶用自己的电脑帮别人交一下网费，结果我的浏览器一开，很大概率的弹出电信的广告窗口，不是每次都弹出，而且有时候在中间，有时候在右下.........

[1]将windows 八安装到移动硬盘中

来源: 互联网发布时间: 2014-02-18

将windows 8安装到移动硬盘中

安装之前将该移动硬盘的该分区设置为主分区并为活动，安装后，进BIOS更改启动项，从移动硬盘启动即可。

注意：WIN$Man这个工具在下面的第一张图片中（将此图片保存在本地，在当前目录新建一个空白的rar文件，在RAR中点左边的“向上”箭头，双击该图片即可，打开该图片即可查看）

[2] Redis windows 测试redis持久化效能

来源: 互联网发布时间: 2014-02-18

Redis windows 测试redis持久化功能

下载地址：servicestack.googlecode.com/files/redis-2.0.2.zip

下载完之后解压到你磁盘上的，我的是F:\redis-2.0.2

还需要在redis根目录增加一个redis的配置文件redis.conf，文件具体内容有：

# Redis configuration file example

# 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 no

# When run as a daemon, Redis write 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
port 6379

# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for connections.
#
# bind 127.0.0.1

# Close the connection after a client is idle for N seconds (0 to disable)
timeout 300

# Set server verbosity to 'debug'
# it can be one of:
# debug (a lot of information, useful for development/testing)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel debug

# Specify the log file name. Also 'stdout' can be used to force
# the demon 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 stdout

# 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
save 900 1
save 300 10
save 60 10000

# 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

# The filename where to dump the DB
dbfilename dump.rdb

# For default save/load DB in/from the working directory
# Note that you must specify a directory not a file name.
dir ./

################################# 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>

################################## 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).
#
# requirepass foobared

################################### LIMITS ####################################

# Set the max number of connected clients at the same time. By default there
# is no limit, and it's up to the number of file descriptors the Redis process
# is able to open. The special value '0' means no limts.
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 128

# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
#
# maxmemory <bytes>

############################## APPEND ONLY MODE ###############################

# By default Redis asynchronously dumps the dataset on disk. If you can live
# with the idea that the latest records will be lost if something like a crash
# happens this is the preferred way to run Redis. If instead you care a lot
# about your data and don't want to that a single record can get lost you should
# enable the append only mode: when this mode is enabled Redis will append
# every write operation received in the file appendonly.log. This file will
# be read on startup in order to rebuild the full dataset in memory.
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
#
# The name of the append only file is "appendonly.log"
#
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.

appendonly yes

# 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 if one second passed since the last fsync. Compromise.
#
# The default is "always" that's the safer of the options. It's up to you to
# understand if you can relax this to "everysec" that will fsync every second
# or to "no" that will let the operating system flush the output buffer when
# it want, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting).

appendfsync always
# appendfsync everysec
# appendfsync no

############################### ADVANCED CONFIG ###############################

# Glue small output buffers together in order to send small replies in a
# single TCP packet. Uses a bit more CPU but most of the times it is a win
# in terms of number of queries per second. Use 'yes' if unsure.
glueoutputbuf yes

# Use object sharing. Can save a lot of memory if you have many common
# string in your dataset, but performs lookups against the shared objects
# pool so it uses more CPU and can be a bit slower. Usually it's a good
# idea.
#
# When object sharing is enabled (shareobjects yes) you can use
# shareobjectspoolsize to control the size of the pool used in order to try
# object sharing. A bigger pool size will lead to better sharing capabilities.
# In general you want this value to be at least the double of the number of
# very common strings you have in your dataset.
#
# WARNING: object sharing is experimental, don't enable this feature
# in production before of Redis 1.0-stable. Still please try this feature in
# your development environment so that we can test it better.
# shareobjects no
# shareobjectspoolsize 1024

启动redis

打开运行窗口

F:\>cd redis-2.0.2

F:\redis-2.0.2>redis-server.exe redis.conf
[2944] 15 Jun 22:44:29 * Server started, Redis version 2.0.2
[2944] 15 Jun 22:44:29 * DB loaded from append only file: 0 seconds
[2944] 15 Jun 22:44:29 * The server is now ready to accept connections on port
379
[2944] 15 Jun 22:44:30 - DB 0: 1 keys (0 volatile) in 4 slots HT.
[2944] 15 Jun 22:44:30 - 0 clients connected (0 slaves), 450888 bytes in use

在打开一个窗口运行客户端

F:\redis-2.0.2>redis-cli.exe

redis>

设置值：

redis> set ajun ajun

Reconnecting... OK
OK

取值：

redis> get ajun
"ajun"

停止redis服务

redis> shutdown

如果需要redis持久化数据需要配置redis日志开启

在每次更新操作后进行日志记录，如果不开启，可能会在断电时导致一段时间内的数据丢失。因为redis本身同步数据文件是按上面save条件来同步的，所以有的数据会在一段时间内只存在于内存中。默认值为no

此时要在redis.conf中修改或者添加

appendonly yes

更新日志文件名，默认值为appendonly.aof

#更新日志条件，共有3个可选值。no表示等操作系统进行数据缓存同步到磁盘，always表示每次更新操作后手动调用fsync()将数据写到磁盘，everysec表示每秒同步一次（默认值）。
# appendfsync always
appendfsync everysec
# appendfsync no

关闭redis 服务在重启

F:\redis-2.0.2>redis-cli.exe

redis>set ajun wahaha

然后在shutdown redis服务

查看appendonly.aof为1k

再启动redis服务

再启动客户端

F:\redis-2.0.2>redis-cli.exe

redis>get ajun
"wahaha"

值还在，说明被持久化了

linux上的操作也是类似的

reids.conf参数配置参考，具体看官方配置文件参数注解

1. redis.conf配置参数：

#是否作为守护进程运行
daemonize yes
#如以后台进程运行，则需指定一个pid，默认为/var/run/redis.pid
pidfile redis.pid
#绑定主机IP，默认值为127.0.0.1
#bind 127.0.0.1
#Redis默认监听端口
port 6379
#客户端闲置多少秒后，断开连接，默认为300（秒）
timeout 300
#日志记录等级，有4个可选值，debug，verbose（默认值），notice，warning
loglevel verbose
#指定日志输出的文件名，默认值为stdout，也可设为/dev/null屏蔽日志
logfile stdout
#可用数据库数，默认值为16，默认数据库为0
databases 16
#保存数据到disk的策略
#当有一条Keys数据被改变是，900秒刷新到disk一次
save 900 1
#当有10条Keys数据被改变时，300秒刷新到disk一次
save 300 10
#当有1w条keys数据被改变时，60秒刷新到disk一次
save 60 10000
#当dump.rdb数据库的时候是否压缩数据对象
rdbcompression yes
#本地数据库文件名，默认值为dump.rdb
dbfilename dump.rdb
#本地数据库存放路径，默认值为 ./
dir /usr/local/redis/var/

########### Replication #####################
#Redis的复制配置
# slaveof <masterip><masterport> 当本机为从服务时，设置主服务的IP及端口
# masterauth<master-password> 当本机为从服务时，设置主服务的连接密码

#连接密码
# requirepass foobared

#最大客户端连接数，默认不限制
# maxclients 128
#最大内存使用设置，达到最大内存设置后，Redis会先尝试清除已到期或即将到期的Key，当此方法处理后，任到达最大内存设置，将无法再进行写入操作。
# maxmemory <bytes>

#是否在每次更新操作后进行日志记录，如果不开启，可能会在断电时导致一段时间内的数据丢失。因为redis本身同步数据文件是按上面save条件来同步的，所以有的数据会在一段时间内只存在于内存中。默认值为no
appendonly no
#更新日志文件名，默认值为appendonly.aof
#appendfilename
#更新日志条件，共有3个可选值。no表示等操作系统进行数据缓存同步到磁盘，always表示每次更新操作后手动调用fsync()将数据写到磁盘，everysec表示每秒同步一次（默认值）。
# appendfsync always
appendfsync everysec
# appendfsync no

################ VIRTUAL MEMORY ###########
#是否开启VM功能，默认值为no
vm-enabled no
# vm-enabled yes
#虚拟内存文件路径，默认值为/tmp/redis.swap，不可多个Redis实例共享
vm-swap-file logs/redis.swap
# 将所有大于vm-max-memory的数据存入虚拟内存,无论vm-max-memory设置多小,所有索引数据都是内存存储的 (Redis的索引数据就是keys),也就是说,当vm-max-memory设置为0的时候,其实是所有value都存在于磁盘。默认值为0。
vm-max-memory 0
vm-page-size 32
vm-pages 134217728
vm-max-threads 4

############# ADVANCED CONFIG ###############
glueoutputbuf yes
hash-max-zipmap-entries 64
hash-max-zipmap-value 512
#是否重置Hash表
activerehashing yes

注意：Redis官方文档对VM的使用提出了一些建议:
** 当你的key很小而value很大时,使用VM的效果会比较好.因为这样节约的内存比较大.
** 当你的key不小时,可以考虑使用一些非常方法将很大的key变成很大的value,比如你可以考虑将key,value组合成一个新的value.
** 最好使用linux ext3 等对稀疏文件支持比较好的文件系统保存你的swap文件.
** vm-max-threads这个参数,可以设置访问swap文件的线程数,设置最好不要超过机器的核数.如果设置为0,那么所有对swap文件的操作都是串行的.可能会造成比较长时间的延迟,但是对数据完整性有很好的保证.

[3] 中国电信牛逼，广告放在浏览器上解决方法

来源: 互联网发布时间: 2014-02-18

中国电信牛逼，广告放在浏览器上
几个月前偶用自己的电脑帮别人交一下网费，结果我的浏览器一开，很大概率的弹出电信的广告窗口，不是每次都弹出，而且有时候在中间，有时候在右下角，真是变幻莫测！
前两天偶抛弃路由，试着把电脑直接连到调制解调器上弄个公有地址上网，结果现在被广告了！
谁能说说电信是怎么做到的？
谁又能说说除了重装系统（重装浏览器偶以前试过了，谷歌、IE都被染上，其他浏览器还不想用），我还有什么办法解决的？
人家告诉我查注册表，都一系列字符数字，偶怎么看啊？

被装了插件了吧革了吧

垄断性行业

它要是硬要插广告的话，你是没有办法的，因为你上网时第一次请求的网页直接被它绑架了，
它把自己的广告嵌入在你请求的网页里，你是没有办法的，你总不能不通过它的交换机吧，
除了投诉，或根据消费者权益保护法和它打官司外，没有什么好办法。

华数宽带天天被强奸，没办法，人家要加广告。

探讨

用火狐

你用了他的物理链路，他给你插什么你就得播放什么。有什么好搞的。没得搞。除非你专门针对他的数据包进行拦截。
探讨

虽然说可能是网页从服务器传回来的时候才被电信添加的广告，但是如果没有直连到电信或者没有用电脑缴费之类的就不会有广告，说明电脑上存在着记录信息或者电信那里记录着我电脑的信息。
然后，我的电脑迁移到不会被污染的地方广告依然弹出，说明，不是电信记录我的信息才广告，而是我电脑上记录了某信息才导致的广告。

电信的，没办法
它是网关一级的，不受本地控制