[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4688: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4690: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4691: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Cheshire Cat Computing :: View topic - Does kMG[] MRTG Option work with routers2.cgi?
Cheshire Cat Computing
http://www.steveshipway.org/forum/

Does kMG[] MRTG Option work with routers2.cgi?
http://www.steveshipway.org/forum/viewtopic.php?f=2&t=93		 Page 1 of 1
Author:  imthemp3king [ Thu Dec 11, 2003 8:24 am ]
Post subject:  Does kMG[] MRTG Option work with routers2.cgi?
I have MRTG running smoothly using rateup and I also have routers2 and rrdtool running simultaneously alongside it. My problem is this. I am using the kMG option in my cfg files for monitoring drive space so that the multiplier prefixes on the graph show up to match the size of the drive. But in the routers2 interface, I cannot get G to show for gigabytes. My MaxBytes is set accordingly and it even lists the the Max on the graph correctly, but it still displays M's on the Y axis instead of G's. It is frustrating because I know the option works fine with plain ol' MRTG and it is displaying just fine on my static pages.

Thanks,
Mike
Author:  stevesh [ Thu Dec 11, 2003 10:20 am ]
Post subject: 
routers.cgi does not support the kmg directive (this is listed in the MRTG_INFO documentation) due to the rrdtool libraries not supporting an equivalent directive. It is in the wishlist to try and work some way to support it.
Usually, the best way to achieve this is to use Factor[] to multiply to the correct units. eg, if your counter returns disk space in MB, then use
Factor[xxxx]: 1024000
to multiply it up to bytes.

Steve
Author:  imthemp3king [ Fri Dec 12, 2003 5:36 am ]
Post subject: 
Thanks for your quick response. I apologize for not thoroughly reading your documentation before posting this question. I have learned my lesson for next time. However, this brings up another question. By using Factor[xxx]: 1024000, I have effectively changed not only the multiplier prefix to the proper designation, but this has increased the displayed MaxBytes for the graph as well. And if I view graphs other than the 6hour graph (daily, weekly, or yearly), the legend units appear correct, but the multiplier prefixes appear greater than they should (T instead of G). Is this bahavior correct, and if so is there any way to use the Factor[xxx]: option without affecting the MaxBytes? Let me know if you would rather I post this message on the MRTG mailing list since I know we are moving away from the forum topic somewhat :wink:

Thanks again for your help,
Mike
Author:  stevesh [ Fri Dec 12, 2003 9:43 am ]
Post subject: 
As I understand the meaning of the Factor[] directive, it should affect only the display of the data, not it's storage in the RRD. So, if the data is being collected (eg) in K, and the max expected value is 1M (=1000K) then you would have
MaxBytes[x] = 1000
Factor[x] = 1024
ShortLegend[x] = b
This would mean the maximum *displayed* value would be 1024000, and the values would be taken from the RRD, multiplied by 1024, and displayed (as bytes).
So, if this is the case, then MaxBytes should indeed be multiplied by the Factor, the same as the data are. A stored value of 1 would be displayed as 1kb, and so on, and the Max line would appear at 1024000 = 1Mb.
The MaxBytes value is the maximum value *stored*, which in the case of this example is in K, not in bytes.

Does this make sense, or have I misunderstood what you are asking?

Steve
Page 1 of 1 All times are UTC + 12 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/