Apache's error log is not very clean: The log messages are mixed with
other web applications' noise; and especially if you use mod_fastcgi,
every line will be prepended with a long prefix.
An alternative is logging to a file. But then you have to make sure that
multiple processes won't corrupt the log file. The module Log::Handler
by Jonny Schulz does exactly this, because it supports message-wise flocking.
This module is a wrapper for said Log::Handler.
text into well formatted documents, including HTML, PDF (by way of
LaTeX), OPML, or OpenDocument (specifically, Flat OpenDocument or
'.fodt', which can in turn be converted into RTF, Microsoft Word, or
virtually any other word-processing format).
MMD is a superset of the Markdown syntax, originally created by John
Gruber. It adds multiple syntax features (tables, footnotes, and
citations, to name a few), in addition to the various output formats
listed above (Markdown only creates HTML). Additionally, it builds in
'smart' typography for various languages (proper left- and right-sided
quotes, for example).
MultiMarkdown was originally a fork of the Markdown Perl code, but as of
version 3.0 has been rewritten as a fork of peg-markdown by John
MacFarlane, written in C. It can be compiled for any major operating
system, and as a native binary runs much faster than the Perl version it
replaces.
NOTE: To use the mmd2pdf script, you must install print/latexmk.
WWW: http://www.fletcherpenney.net/multimarkdown/
Note. The 2.2.15 release is the latest release from
legacy 2.2 branch. Next commit is up to latest bugfix
release from 2.4 branch.
<ChangeLog>
* [BUGFIX] FLUSHALL was not replicated nor written into the
Append Only File.
* [BUGFIX] FLUSHALL now only performs a sync SAVE if there
is at least one save point configured.
</ChangeLog>
interface graphs for a device on the same screen. This helps with spotting
trends, or tracing where traffic is flowing through a switch or router. The
only way to natively achieve this with Zenoss is to create a graph or
multi-graph report for every network device manually, which can be a chore
if you have more than a few network devices.
This ZenPack provides a new link on the left side of a device detail view
called "Interface Graphs" - this view shows the graphs for all of the network
interfaces on the device in one place, allowing for fast spotting of issues
or traffic flows. Both the interface name and the description (if any) are
used to title the graphs to aid with identification.
Note that with stacked switches, you can end up with a very large number of
graphs on the page, so tuning this slightly via the configuration properties
below could be a good idea in these situations.
WWW: http://community.zenoss.org/docs/DOC-10226
PR: ports/157503
Submitted by: Zenoss <zenoss@experts-exchange.com>
2011-11-04 astro/weatherget: Broken b/c of weather.com new licensing rules not agreed by author
2011-11-04 devel/py-reverse: Now part of pylint
2011-11-04 devel/py-vmaps: Author recommends using math/py-numpy instead
PR: ports/161063 ports/161067 ports/161074
Submitted by: Ruslan Mahmatkhanov <cvs-src@yandex.ru>
