Give context to these logging error messages.
authorMichael M Slusarz <slusarz@curecanti.org>
Wed, 6 Oct 2010 15:32:23 +0000 (09:32 -0600)
committerMichael M Slusarz <slusarz@curecanti.org>
Wed, 6 Oct 2010 17:28:55 +0000 (11:28 -0600)
commitf957ed089923f9bcf7512afa32d5feee67ee242a
treeb79018fa738f0949f510d942dc3db942ac199cdc
parent0b767eec3c571a62accb018c0a58b90d88c96447
Give context to these logging error messages.

Probably should go through the entire Log library and upgrade the
exception error messages.  Since these messages can't be logged
themeselves (for obvious reasons), they need to be very clear in order
to track down the issue.

Example: today, I got a 'stream could not be written' fatal error (my
logging temp drive was full).  However, it was not immediately obvious
from the error message what subsystem failed.
framework/Log/lib/Horde/Log/Handler/Stream.php