[
https://issues.apache.org/jira/browse/QPID-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-1361.
--------------------------------
Resolution: Fixed
Fix Version/s: M4
Checked in (if you've read the diff file attached, the valgrind suppressions
are _NOT_ in the actual check-in). SVN revision 705083.
> C++ - allow platform-specific logging sinks in order to support non-posix
> platforms
> -----------------------------------------------------------------------------------
>
> Key: QPID-1361
> URL: https://issues.apache.org/jira/browse/QPID-1361
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, C++ Client
> Reporter: Steve Huston
> Assignee: Steve Huston
> Fix For: M4
>
> Attachments: logging.diff
>
>
> The current C++ code has options that affect run-time logging. The
> information and level selectors are portable. The options affecting the
> logging sinks are not. There was a recent exchange on qpid-dev concerning how
> best to handle adding Windows logging sink options. The end result was a
> change from the multiple --log-output possibilities to:
> Logging sink options:
> --log-to-stderr yes|no (1) Send logging output to stderr
> --log-to-stdout yes|no (0) Send logging output to stdout
> --log-to-file FILE Send log output to FILE.
> --log-to-syslog yes|no (0) Send logging output to syslog;
> customize using --syslog-name and
> --syslog-facility
> --syslog-name NAME (lt-qpidd) Name to use in syslog messages
> --syslog-facility LOG_XXX (LOG_DAEMON) Facility to use in syslog messages
> On Windows, these will be different, in that there's no syslog. There will
> probably be something directing to the system event log and possibly some
> event log-specific options. Other platforms may have other possibilities and
> may or may not have stderr/stdout options. It's now dependent on the platform
> what the logging sinks are.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
