Zabbix的配置文件一般有三种:

  • zabbix_server.conf:zabbix server的配置文件
  • zabbix_proxy.conf:zabbix proxy的配置文件
  • zabbix_agentd.conf:zabbix agentd的配置文件

Zabbix安装完成后,服务端默认的配置文件存在安装文件夹中的etc目录中,假设编译的参数是“--prefix=/usr/local/zabbix”,那么服务端的配置文件则保存在“/usr/loca/zabbix/etc/”目录下。zabbix_server.conf参数除了保证服务正常运行外,还会影响服务器的性能。如果参数设定不合理可能会导致zabbix添加主机不正常、代理端数据无法正常收集或是zabbix服务器性能严重下降,经常报告CPU占用过高或是IO占用过高等问题。本文说明了zabbix server的配置文件中的通用参数和大部分高级参数的具体用法,内容如下:

  1. ############ GENERAL PARAMETERS #################
  2.  
  3. ### Option: ListenPort
  4. # Listen port for trapper.
  5. //该参数用于指定服务端的监听端口,用于监听Proxy或Agent的连接请求。
  6. #
  7. # Mandatory: no
  8. # Range: 1024-32767
  9. # Default:
  10. # ListenPort=10051
  11.  
  12. ### Option: SourceIP
  13. # Source IP address for outgoing connections.
  14. //该参数用于指定服务端的IP地址。
  15. #
  16. # Mandatory: no
  17. # Default:
  18. # SourceIP=
  19.  
  20. ### Option: LogType
  21. # Specifies where log messages are written to://zabbix的日志类型
  22. # system - syslog //写入到系统日志
  23. # file - file specified with LogFile parameter //写入到指定文件
  24. # console - standard output //写入到标准输出
  25. #
  26. # Mandatory: no
  27. # Default:
  28. # LogType=file
  29.  
  30. ### Option: LogFile
  31. # Log file name for LogType 'file' parameter.
  32. //日志文件的存储路径
  33. #
  34. # Mandatory: no
  35. # Default:
  36. # LogFile=
  37.  
  38. LogFile=/tmp/zabbix_server.log
  39.  
  40. ### Option: LogFileSize
  41. # Maximum size of log file in MB.
  42. # 0 - disable automatic log rotation.
  43. //指定日志文件的大小,单位MB。0表示禁用日志轮转
  44. #
  45. # Mandatory: no
  46. # Range: 0-1024
  47. # Default:
  48. # LogFileSize=1
  49.  
  50. ### Option: DebugLevel
  51. # Specifies debug level: //指定debug级别
  52. # 0 - basic information about starting and stopping of Zabbix processes //关于进程启动和停止的基本信息
  53. # 1 - critical information //关键信息
  54. # 2 - error information //错误信息
  55. # 3 - warnings //警告
  56. # 4 - for debugging (produces lots of information) //调试信息
  57. # 5 - extended debugging (produces even more information)
  58. #
  59. # Mandatory: no
  60. # Range: 0-5
  61. # Default:
  62. # DebugLevel=3
  63.  
  64. ### Option: PidFile
  65. # Name of PID file.
  66. //pid文件名
  67. #
  68. # Mandatory: no
  69. # Default:
  70. # PidFile=/tmp/zabbix_server.pid
  71.  
  72. ### Option: DBHost
  73. # Database host name.
  74. # If set to localhost, socket is used for MySQL.
  75. # If set to empty string, socket is used for PostgreSQL.
  76. //数据库主机名,如果设置为localhost,mysql必须用socket来连接,否则用ip来连接。若该参数为空,默认连接PostgreSQL
  77. #
  78. # Mandatory: no
  79. # Default:
  80. # DBHost=localhost
  81.  
  82. ### Option: DBName
  83. # Database name.
  84. # For SQLite3 path to database file must be provided. DBUser and DBPassword are ignored.
  85. //数据库名。对SQLite3来说,必须提供数据文件的路径,DBUser和DBPassword参数可忽略
  86. #
  87. # Mandatory: yes
  88. # Default:
  89. # DBName=
  90.  
  91. ### Option: DBSchema
  92. # Schema name. Used for IBM DB2 and PostgreSQL.
  93. //模式名。用于DB2或PostgreSQL数据库
  94. #
  95. # Mandatory: no
  96. # Default:
  97. # DBSchema=
  98.  
  99. ### Option: DBUser
  100. # Database user. Ignored for SQLite.
  101. //连接数据库的用户名,SQLite忽略该参数
  102. #
  103. # Mandatory: no
  104. # Default:
  105. # DBUser=
  106.  
  107. ### Option: DBPassword
  108. # Database password. Ignored for SQLite.
  109. # Comment this line if no password is used.
  110. //连接数据库的密码,SQLite忽略该参数
  111. #
  112. # Mandatory: no
  113. # Default:
  114. # DBPassword=
  115.  
  116. ### Option: DBSocket
  117. # Path to MySQL socket.
  118. //socket文件的路径
  119. #
  120. # Mandatory: no
  121. # Default:
  122. # DBSocket=/tmp/mysql.sock
  123.  
  124. ### Option: DBPort
  125. # Database port when not using local socket. Ignored for SQLite.
  126. //数据库监听端口,SQLite忽略该参数
  127. #
  128. # Mandatory: no
  129. # Range: 1024-65535
  130. # Default (for MySQL):
  131. # DBPort=3306
  132.  
  133. ############ ADVANCED PARAMETERS ################
  134.  
  135. ### Option: StartPollers
  136. # Number of pre-forked instances of pollers.
  137. //系统初始化时,预分配子进程数量。数量越多,则服务端吞吐能力越强,对系统资源消耗越大。
  138. #
  139. # Mandatory: no
  140. # Range: 0-1000
  141. # Default:
  142. # StartPollers=5
  143.  
  144. ### Option: StartIPMIPollers
  145. # Number of pre-forked instances of IPMI pollers.
  146. //系统初始化时,预分配的使用ipmi协议获取主机硬件状态的进程数量。
  147. #
  148. # Mandatory: no
  149. # Range: 0-1000
  150. # Default:
  151. # StartIPMIPollers=0
  152.  
  153. ### Option: StartPollersUnreachable
  154. # Number of pre-forked instances of pollers for unreachable hosts (including IPMI and Java).
  155. # At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers
  156. # are started.
  157. //系统初始化时,预分配用于探测某些不可达主机的(含IPMI、JAVA)的进程数量;若使用场景中含有代理端,建议保持默认;若Agent较多,可视具体情况调整。
  158. #
  159. # Mandatory: no
  160. # Range: 0-1000
  161. # Default:
  162. # StartPollersUnreachable=1
  163.  
  164. ### Option: StartTrappers
  165. # Number of pre-forked instances of trappers.
  166. # Trappers accept incoming connections from Zabbix sender, active agents and active proxies.
  167. # At least one trapper process must be running to display server availability and view queue
  168. # in the frontend.
  169. //系统初始化时,预分配的用于接收zabbix sender提交来数据的进程。
  170. #
  171. # Mandatory: no
  172. # Range: 0-1000
  173. # Default:
  174. # StartTrappers=5
  175.  
  176. ### Option: StartPingers
  177. # Number of pre-forked instances of ICMP pingers.
  178. //系统初始化时,预分配的icmp ping进程的数量。若单台代理所管理机器超过500台,建议加大此数值
  179. #
  180. # Mandatory: no
  181. # Range: 0-1000
  182. # Default:
  183. # StartPingers=1
  184.  
  185. ### Option: StartDiscoverers
  186. # Number of pre-forked instances of discoverers.
  187. //系统初始化时,预分配的自动发现主机的线程数量。若单台代理所管理机器超过500台,可以考虑加大此数值(仅适用于AGENT场景)
  188. #
  189. # Mandatory: no
  190. # Range: 0-250
  191. # Default:
  192. # StartDiscoverers=1
  193.  
  194. ### Option: StartHTTPPollers
  195. # Number of pre-forked instances of HTTP pollers.
  196. //系统预分配的用于设置WEB监控进程数,可视具体情况增加或减少此数值。
  197. #
  198. # Mandatory: no
  199. # Range: 0-1000
  200. # Default:
  201. # StartHTTPPollers=1
  202.  
  203. ### Option: StartTimers
  204. # Number of pre-forked instances of timers.
  205. # Timers process time-based trigger functions and maintenance periods.
  206. # Only the first timer process handles the maintenance periods.
  207. //各实例计时器数量
  208. #
  209. # Mandatory: no
  210. # Range: 1-1000
  211. # Default:
  212. # StartTimers=1
  213.  
  214. ### Option: StartEscalators
  215. # Number of pre-forked instances of escalators.
  216. #
  217. # Mandatory: no
  218. # Range: 0-100
  219. # Default:
  220. # StartEscalators=1
  221.  
  222. ### Option: StartVMwareCollectors
  223. # Number of pre-forked vmware collector instances.
  224. //用于监控VMWARE Esxi主机实例的进程数量,为0则不启用,若要监控ESXI主机,此值最少为1 ;视监控ESXI数量设置对应数值
  225. #
  226. # Mandatory: no
  227. # Range: 0-250
  228. # Default:
  229. # StartVMwareCollectors=0
  230.  
  231. ### Option: VMwareFrequency
  232. # How often Zabbix will connect to VMware service to obtain a new data.
  233. //Zabbix连接WMware service获取新数据的频率
  234. #
  235. # Mandatory: no
  236. # Range: 10-86400
  237. # Default:
  238. # VMwareFrequency=60
  239.  
  240. ### Option: VMwarePerfFrequency
  241. # How often Zabbix will connect to VMware service to obtain performance data.
  242. #
  243. # Mandatory: no
  244. # Range: 10-86400
  245. # Default:
  246. # VMwarePerfFrequency=60
  247.  
  248. ### Option: VMwareCacheSize
  249. # Size of VMware cache, in bytes.
  250. # Shared memory size for storing VMware data.
  251. # Only used if VMware collectors are started.
  252. //用于缓存VMware数据的共享内存
  253. #
  254. # Mandatory: no
  255. # Range: 256K-2G
  256. # Default:
  257. # VMwareCacheSize=8M
  258.  
  259. ### Option: VMwareTimeout
  260. # Specifies how many seconds vmware collector waits for response from VMware service.
  261. #
  262. # Mandatory: no
  263. # Range: 1-300
  264. # Default:
  265. # VMwareTimeout=10
  266.  
  267. ### Option: SNMPTrapperFile
  268. # Temporary file used for passing data from SNMP trap daemon to the server.
  269. # Must be the same as in zabbix_trap_receiver.pl or SNMPTT configuration file.
  270. #
  271. # Mandatory: no
  272. # Default:
  273. # SNMPTrapperFile=/tmp/zabbix_traps.tmp
  274.  
  275. ### Option: StartSNMPTrapper
  276. # If 1, SNMP trapper process is started.
  277. //是否启用snmptrapper功能 ,默认不启用=0,启用=1
  278. #
  279. # Mandatory: no
  280. # Range: 0-1
  281. # Default:
  282. # StartSNMPTrapper=0
  283.  
  284. ### Option: ListenIP
  285. # List of comma delimited IP addresses that the trapper should listen on.
  286. # Trapper will listen on all network interfaces if this parameter is missing.
  287. #
  288. # Mandatory: no
  289. # Default:
  290. # ListenIP=0.0.0.0
  291. # ListenIP=127.0.0.1
  292.  
  293. ### Option: HousekeepingFrequency
  294. # How often Zabbix will perform housekeeping procedure (in hours).
  295. # Housekeeping is removing outdated information from the database.
  296. # To prevent Housekeeper from being overloaded, no more than 4 times HousekeepingFrequency
  297. # hours of outdated information are deleted in one housekeeping cycle, for each item.
  298. # To lower load on server startup housekeeping is postponed for 30 minutes after server start.
  299. # With HousekeepingFrequency=0 the housekeeper can be only executed using the runtime control option.
  300. # In this case the period of outdated information deleted in one housekeeping cycle is 4 times the
  301. # period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.
  302. //多少小时清理一次数据库的 history, alert, and alarms数据
  303. #
  304. # Mandatory: no
  305. # Range: 0-24
  306. # Default:
  307. # HousekeepingFrequency=1
  308.  
  309. ### Option: MaxHousekeeperDelete
  310. # The table "housekeeper" contains "tasks" for housekeeping procedure in the format:
  311. # [housekeeperid], [tablename], [field], [value].
  312. # No more than 'MaxHousekeeperDelete' rows (corresponding to [tablename], [field], [value])
  313. # will be deleted per one task in one housekeeping cycle.
  314. # SQLite3 does not use this parameter, deletes all corresponding rows without a limit.
  315. # If set to 0 then no limit is used at all. In this case you must know what you are doing!
  316. //housekeeping一次删除的数据不能大于MaxHousekeeperDelete
  317. #
  318. # Mandatory: no
  319. # Range: 0-1000000
  320. # Default:
  321. # MaxHousekeeperDelete=5000
  322.  
  323. ### Option: SenderFrequency
  324. # How often Zabbix will try to send unsent alerts (in seconds).
  325. //指定间隔多少秒后,再尝试发送为发送的报警
  326. #
  327. # Mandatory: no
  328. # Range: 5-3600
  329. # Default:
  330. # SenderFrequency=30
  331.  
  332. ### Option: CacheSize
  333. # Size of configuration cache, in bytes.
  334. # Shared memory size for storing host, item and trigger data.
  335. //分配多少共享内存用于存储配置信息,HOST,ITEM,TRIGGER数据,视监控主机数量和监控项调整,建议调整到32M或者更大,2.2.3版本之前最大支持2G,目前最大支持8G,一般用不了多少。
  336. #
  337. # Mandatory: no
  338. # Range: 128K-8G
  339. # Default:
  340. # CacheSize=8M
  341.  
  342. ### Option: CacheUpdateFrequency
  343. # How often Zabbix will perform update of configuration cache, in seconds.
  344. //更新系统CACHE频率,若管理页面操作不频繁,可以考虑加大参数值
  345. #
  346. # Mandatory: no
  347. # Range: 1-3600
  348. # Default:
  349. # CacheUpdateFrequency=60
  350.  
  351. ### Option: StartDBSyncers
  352. # Number of pre-forked instances of DB Syncers.
  353. //将采集数据从CACHE同步到数据库线程数量,视数据库服务器I/O繁忙情况,和数据库写能力调整。数值越大,写能力越强。对数据库服务器I/O压力越大。
  354. #
  355. # Mandatory: no
  356. # Range: 1-100
  357. # Default:
  358. # StartDBSyncers=4
  359.  
  360. ### Option: HistoryCacheSize
  361. # Size of history cache, in bytes.
  362. # Shared memory size for storing history data.
  363. //设置划分多少共享内存用于存储采集的历史数据,此数值越大,数据库读压力越小
  364. #
  365. # Mandatory: no
  366. # Range: 128K-2G
  367. # Default:
  368. # HistoryCacheSize=16M
  369.  
  370. ### Option: HistoryIndexCacheSize
  371. # Size of history index cache, in bytes.
  372. # Shared memory size for indexing history cache.
  373. //历史数据索引缓存
  374. #
  375. # Mandatory: no
  376. # Range: 128K-2G
  377. # Default:
  378. # HistoryIndexCacheSize=4M
  379.  
  380. ### Option: TrendCacheSize
  381. # Size of trend cache, in bytes.
  382. # Shared memory size for storing trends data.
  383. //用于设置划分多少共享内存用于存储计算出来的趋势数据,此参数值从一定程度上可影响数据库读压力
  384. #
  385. # Mandatory: no
  386. # Range: 128K-2G
  387. # Default:
  388. # TrendCacheSize=4M
  389.  
  390. ### Option: ValueCacheSize
  391. # Size of history value cache, in bytes.
  392. # Shared memory size for caching item history data requests.
  393. # Setting to 0 disables value cache.
  394. //0表示禁用,history value缓存大小,当缓存超标了,将会每隔5分钟往server日志里面记录。
  395. #
  396. # Mandatory: no
  397. # Range: 0,128K-64G
  398. # Default:
  399. # ValueCacheSize=8M
  400.  
  401. ### Option: Timeout
  402. # Specifies how long we wait for agent, SNMP device or external check (in seconds).
    //与AGNET、SNMP设备和其它外部设备通信超时设置,单位为秒;若采集数据不完整或网络繁忙,或从管理页面发现客户端状态变化频繁,可以考虑加大此数值。注意若此数值加大,应该考虑参数StartPollers 是否有相应加大的必要。
  403. #
  404. # Mandatory: no
  405. # Range: 1-30
  406. # Default:
  407. # Timeout=3
  408.  
  409. ### Option: TrapperTimeout
  410. # Specifies how many seconds trapper may spend processing new data.
  411. //启用trapper功能,用于进程等待超时设置。
  412. #
  413. # Mandatory: no
  414. # Range: 1-300
  415. # Default:
  416. # TrapperTimeout=300
  417.  
  418. ### Option: UnreachablePeriod
  419. # After how many seconds of unreachability treat a host as unavailable.
  420. //当Agent端处于不可用状态下,间隔多少秒后,尝试重新连接。建议根据具体情况设置。注意,若此数值过小,若Agent端业务系统繁忙时,有可能造成报警误报
  421. #
  422. # Mandatory: no
  423. # Range: 1-3600
  424. # Default:
  425. # UnreachablePeriod=45
  426.  
  427. ### Option: UnavailableDelay
  428. # How often host is checked for availability during the unavailability period, in seconds.
    //当Agent端处于不可用状态下,间隔多少秒后,进行状态检查。若出现可正常采集数据,但管理页面AGENT状态不正常、或在网络,端口等均通畅情况下,AGENT状态仍不正常,可以考虑加大此数值
  429. #
  430. # Mandatory: no
  431. # Range: 1-3600
  432. # Default:
  433. # UnavailableDelay=60
  434.  
  435. ### Option: UnreachableDelay
  436. # How often host is checked for availability during the unreachability period, in seconds.
  437. //当Agent端处于不可达状态下,延迟多少秒后,进行重新尝试,建议保持默认,在AGENT接入调试阶段,可考虑减少此数值
  438. #
  439. # Mandatory: no
  440. # Range: 1-3600
  441. # Default:
  442. # UnreachableDelay=15
  443.  
  444. ### Option: AlertScriptsPath
  445. # Full path to location of custom alert scripts.
  446. # Default depends on compilation options.
  447. //自定义告警脚本存放全路径
  448. #
  449. # Mandatory: no
  450. # Default:
  451. # AlertScriptsPath=${datadir}/zabbix/alertscripts
  452.  
  453. ### Option: LogSlowQueries
  454. # How long a database query may take before being logged (in milliseconds).
  455. # Only works if DebugLevel set to 3, 4 or 5.
  456. # 0 - don't log slow queries.
  457. //用于服务端数据库慢查询功能,单位是毫秒。若有服务端数据库监控慢查询的需求,可以视具体情况调整此数。
  458. #
  459. # Mandatory: no
  460. # Range: 1-3600000
  461. # Default:
  462. # LogSlowQueries=0
  463.  
  464. ### Option: TmpDir
  465. # Temporary directory.
  466. //指定临时目录路径
  467. #
  468. # Mandatory: no
  469. # Default:
  470. # TmpDir=/tmp
  471.  
  472. ### Option: StartProxyPollers
  473. # Number of pre-forked instances of pollers for passive proxies.
  474. //启用多少子进程与代理端通信,若代理端较多可考虑加大此数值
  475. #
  476. # Mandatory: no
  477. # Range: 0-250
  478. # Default:
  479. # StartProxyPollers=1
  480.  
  481. ### Option: ProxyConfigFrequency
  482. # How often Zabbix Server sends configuration data to a Zabbix Proxy in seconds.
  483. # This parameter is used only for proxies in the passive mode.
  484. //Zabbix服务端将配置文件数据同步到代理端的频率,仅适用于代理端为被动模式情况
  485. #
  486. # Mandatory: no
  487. # Range: 1-3600*24*7
  488. # Default:
  489. # ProxyConfigFrequency=3600
  490.  
  491. ### Option: ProxyDataFrequency
  492. # How often Zabbix Server requests history data from a Zabbix Proxy in seconds.
  493. # This parameter is used only for proxies in the passive mode.
  494. //Zabbix服务端请求代理端采集的数据的频率,仅适用代理端为被动模式情况
  495. #
  496. # Mandatory: no
  497. # Range: 1-3600
  498. # Default:
  499. # ProxyDataFrequency=1
  500.  
  501. ### Option: AllowRoot
  502. # Allow the server to run as 'root'. If disabled and the server is started by 'root', the server
  503. # will try to switch to the user specified by the User configuration option instead.
  504. # Has no effect if started under a regular user.
  505. # 0 - do not allow
  506. # 1 - allow
  507. //是否允许以root身份运行服务端
  508. #
  509. # Mandatory: no
  510. # Default:
  511. # AllowRoot=0
  512.  
  513. ### Option: User
  514. # Drop privileges to a specific, existing user on the system.
  515. # Only has effect if run as 'root' and AllowRoot is disabled.
  516. //启动zabbix server的用户,在配置禁止root启动,并且当前shell用户是root得情况下有效。如果当前用户是abc,那么zabbix server的运行用户是abc
  517. #
  518. # Mandatory: no
  519. # Default:
  520. # User=zabbix
  521.  
  522. ### Option: Include
  523. # You may include individual files or all files in a directory in the configuration file.
  524. # Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
  525. //某些情况下,软件的参数配置文件很长,为了方便管理,将配置文件切割成N个配置文件,但为了主配置参数文件的简洁,便会启用INCLUDE参数,以方便程序读取指定目录下的所有配置文件
  526. #
  527. # Mandatory: no
  528. # Default:
  529. # Include=
  530.  
  531. # Include=/usr/local/etc/zabbix_server.general.conf
  532. # Include=/usr/local/etc/zabbix_server.conf.d/
  533. # Include=/usr/local/etc/zabbix_server.conf.d/*.conf

Zabbix Server参数文件详解的更多相关文章

  1. server.properties 文件详解

    [转载]:server.properties 文件详解 # 每一个Broker在集群中的唯标识.即使Broker的IP地址发生了变化,broker.id只要没变,则不会影响consumers的消息情况 ...

  2. server.xml文件详解

    一.server.xml文件介绍 1.server.xml作用     Server.xml配置文件用于对整个容器进行相关的配置. 2.server.xml文件的配置元素列表 <Server&g ...

  3. Tomcat 的 server.xml 文件详解

    文件内容解读 <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apac ...

  4. VSFTPD全攻略(/etc/vsftpd/vsftpd.conf文件详解)

    /etc/vsftpd/vsftpd.conf文件详解,分好类,方便大家查找与学习 #################匿名权限控制############### anonymous_enable=YE ...

  5. /etc/inittab文件详解

    /etc/inittab由/sbin/init程序解析调用,用于系统初始化,/sbin/init可参考源码busybox中init.c的实现方式. 原址如下: http://leejia.blog.5 ...

  6. Angular Npm Package.Json文件详解

    Angular7 Npm Package.Json文件详解   近期时间比较充裕,正好想了解下Angular Project相关内容.于是将Npm官网上关于Package.json的官方说明文档进行了 ...

  7. Linux下inittab文件详解

    /etc/inittab文件详解 Linux系统的启动过程为:加电自检-->根据BIOS中的设置从指定的设备启动-->找到设备MBR中的bootloader引导启动系统-->启动ke ...

  8. C#中web.config文件详解

    C#中web.config文件详解 一.认识Web.config文件 Web.config 文件是一个XML文本文件,它用来储存 ASP.NET Web 应用程序的配置信息(如最常用的设置ASP.NE ...

  9. vue-cli生成的模板各个文件详解(转)

    vue-cli脚手架中webpack配置基础文件详解 一.前言 原文:https://segmentfault.com/a/1190000014804826 vue-cli是构建vue单页应用的脚手架 ...

随机推荐

  1. How Can You Tell the Difference Between LINQ Methods and Query Builder Methods?

    LINQ's method syntax looks very similar to the query builder methods,except for one big difference:t ...

  2. 关于字符串不为空 错误:s!=null

    错误:s!=null 正确:StringUtils.isNotBlank(s); public static boolean isBlank(CharSequence cs) { int strLen ...

  3. 在JQuery中$(document.body)和这个$("body") 这两的区别在哪里?

    两种写法代表的是同一个对象 $("body") 是一个选择器,jQuery 会从 DOM 顶端开始搜索,直到找到标签为 body 的元素. 而 $(document.body) 中 ...

  4. jquery ajax获取json并解析,获取的json是object对象格式

    首先我们使用的是ajax方式,推荐一个学习网址: http://blog.csdn.net/shiyaru1314/article/details/51065410 这个博主写的特别好.现在来看我们的 ...

  5. C# 运行CMD命令

    /// <summary> /// 运行CMD命令 /// </summary> /// <param name="cmd">命令</pa ...

  6. poj 1331 Multiply

    Multiply Time Limit: 1000MS   Memory Limit: 10000K Total Submissions: 5179   Accepted: 2773 Descript ...

  7. UIWebView 设置背景为透明

    UIWebView的背景怎样设置成为透明? [webview setBackgroundColor:[UIColor clearColor]]; [webview setOpaque:NO]; 两句代 ...

  8. The return type is incompatible with JspSourceDependent.getDependants():JasperException问题分析与解决方法

    Linux下基于JSP的报表集成到项目中后,显示不出来,查看tomcat的日志.有例如以下报错信息: The return type is incompatible with JspSourceDep ...

  9. HttpClient的Post和Get訪问网页

    一.基础JAR包 Mavenproject下pom.xml需配置的jar包 <dependencies> <dependency> <groupId>junit&l ...

  10. Android中不同方向嵌套滑动的解决方式(ListView为样例)

    前言: 就像手机QQ的聊天消息列表.一个纵向滑动的ListView列举全部消息,但每一条消息能够横向滑动. 而默认情况下,仅仅能有一个地方消化处理触摸事件,要么ListView吃掉这个事件.要么子It ...