Thanks, this seems to do the trick perfectly :-) In reply to Ged: it's not as much about security concerns, as it's about resource concerns, and even before real "concerns" -- I just try to do things with the minimal required overhead. If I can do it with less, I'll try to do it with less :-) Smokeping is exacly what I need right now (I need good delay and jitter information on a single link, nicely graphed) but then again it is much more than I need (I don't need notifications, web interface etc.)
regards, Zoltan On 11/20/2009 2:14 PM, Tobias Oetiker wrote: > Hi Kelemen, > > have a look at the --static option in smokeping ... > > cheers > tobi > > Today Kelemen Zoltán wrote: > > >> Hi, >> >> I'm looking for a way to run smokeping& generate it's graphs without >> running it through a webserver. >> >> Sincerely, I don't need a fancy webpage, I don't need menus and I might >> want to get away with something more lightweight than a cgi-enabled >> apache installation. I only need the graphs that are rendered. >> >> It should be simple enough as it is a perl script after all, and running >> the script will update my overview/"*_mini" graphs. However, to update >> the detail graphs, the script seems to expect GET parameters of a http >> request. Is there a way around this? Could the smokeping graphs be >> generated somehow from the command line? >> >> thanks, >> Zoltan >> >> _______________________________________________ >> smokeping-users mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users >> >> >> > _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
