Rearrange the secure monitor section after reviewing
Update the secure conns docs re monitor db setup
Fix some inaccuracies (out-of-date) in the intro pcp-doc
Remove reference to -n (namespace) in docs, unhelpful
Consistent use of bold for commands in intro doc
Update the secure connections document with many recent changes

In particular, reworked to use better certutil incantations based
on Dave's detective work.  Also redid the pmchart screenshot with
current expectations, added an ico file, and many text updates to
make it a more gripping read.
Add a consistent ico file for all the tutorials/howtos
Fix typo in secure conns doc, thanks fche (for the fix, not the typo)
Correct the collector certificate subject, as Dave noted
Extensions to the New Host dialog box allowing

Allowing secure connections to be explicitly requested, and
also invoking the nss-gui NSS certificate database frontend
application for certificate management.
Update license details as per email from SGI legal folks
PCP_PG: drop sgml artifacts, retain only working docbook-xml source
PCP_UAG: drop sgml artifacts, retain only working docbook-xml source
PCP_PG: publican enablement
PCP_UAG: publican enablement
add emacs .dir-local.el for formatting preferences
QString toAscii decorruption

A recurrent coding pattern in the code aimed to get C "const char*"
pointers out of QString objects, with code that looks like this:

          (const char*) object.toAscii()

This is wrong on several levels.  In Qt4 and probably earlier,
toAscii() returns a (temporary) QByteArray object, not a C string.
Any casting to hide this leads to direct junk, e.g., failure to save
pmchart view state to requested file names, or with actual readable
metric names.  We switch to

          object.toAscii().constData()

throughout.  This too is imperfect, as the QByteArray object is
temporary, and will be deallocated at the next statement (;) boundary,
which makes the const char*'s contain junk again.  So, cases where
such pointers are stored beyond a statement need to be strdup()'d.
Revert "QString toAscii decorruption"

This reverts commit b6b7de7ce33eded33f18a6d1d89c33a0d373957a.

We may need to only handle those cases where the returned
    (const char*) qstring.toAscii()
value is saved across statements.
Give ChartEngine a dummy virtual destructor

That way, the compiler doesn't complain about "delete aChargEnginePtr".
QString toAscii decorruption

A recurrent coding pattern in the code aimed to get C "const char*"
pointers out of QString objects, with code that looks like this:

          (const char*) object.toAscii()

This is OK, using the QByteArray conversion-operator, as long as the
value is used before the QByteArray temporary is itself deleted.
However, in a few cases, the value is instead stored, or returned,
leading to corruption and deceit.  These have been reworked:

* src/chart/chartdialog.cpp (createChartPlot): strdup the nlabel.
* src/chart/colorscheme.cpp (colorSpec): Inline the rgbi string.
* src/chart/exportdialog.cpp (exportFile): Inline the strcmp args.
* src/chart/view.cpp (saveChart): Simplify and inline metric
  name/instance strings.
  (saveView): strdup incoming file name.
* src/libqmc/qmc_metric.h (*Ascii()): strdup return value.
* src/libqmc/qmc_source.h (*Ascii()): strdup return value.