Chinaunix首页 | 论坛 | 博客
  • 博客访问: 561439
  • 博文数量: 375
  • 博客积分: 0
  • 博客等级: 民兵
  • 技术积分: 15
  • 用 户 组: 普通用户
  • 注册时间: 2013-09-20 10:21
文章分类

全部博文(375)

文章存档

2015年(1)

2014年(374)

分类: LINUX

2014-08-18 11:05:14

Run as the given user and/or group. (Unix Only)

 

Use an alternate lock-file (the default is to use the configuration-file appended with _l).

Use an alternate confcache-file (the default is to use the configuration-file appended with .ok)

 

If this is set to writable filename, all output from mrtg (warnings, debug messages, errors) will go to filename. If you are running on Win32 you can specify eventlog instead of a filename which will send all error to the windows event log.

NOTE: Note, there is no Message DLL for mrtg included with mrtg. This has the side effect that the windows event logger will display a nice message with every entry in the event log, complaing about the fact that mrtg has no message dll. If you go to the mrtg contrib download area (on the website) you will find the mrtg-message-dll.zip which does contain such a thing.

Put MRTG into the background, running as a daemon. This works the same way as the config file option, but the switch is required for proper FHS operation (because /var/run is writable only by root)

Configure all mrtg paths to conform to the FHS specification;

Only check the cfg file for errors. Do not do anything.

Define the name and path of the pid file for mrtg running as a daemon

Enable debug options. The argument of the debug option is a comma separated list of debug values:

cfg  - watch the config file reading

dir  - directory mangeling

base - basic program flow

tarp - target parser

snpo - snmp polling

coca - confcache operations

fork - forking view

time - some timing info

log  - logging of data via rateup or rrdtool

Example:

--debug="cfg,snpo"

 

 


 

 

An exit code of 0 indicates that all targets were successful. Generally speaking, most codes greater than 0 indicate that there was an unrecoverable problem. One exception to this is code 91, which indicates that at least one of the targets was succesful. A partial listing of the codes follows:

 

# 注释 :MRTG 的 exit code 有几种 :

 

#     -)0 :一切正常

 

#     -)2 :配置错误

 

#     -)17 :另外的 MRTG 进程在运行

 

#     -)91 :至少有一个 Target 正常

 

#     -)92 :所有的 Target 都失败


 

0: All targets sucessful 

2: Config error (can't read, fatal error in config, etc)

17: Another MRTG process is processing config 

91: At least one target sucessful

92: No targets were sucessful

 

阅读(474) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~