Craig Bennett wrote:
Wally,
Collect your thoughts and funnel them thru the U2UG Better and Better
committee...
That is likely a better way than flooding this list. Just my
recommendation.
As a UV user I don't mind what happens to UniData; but wouldn't it be
great if UV and UD logged to syslog (every platform except windows) or
the windows error logs?
All of a sudden monitoring U2 errors is just like any other installed
program -- sysadmins feel good, logs get rotated and archived in a
standard way. And everyone knows where to look even if they haven't read
a U2 manual.
Surely this couldn't be that much harder than implementing your own
logging system?
For bonus points expose the system logging functionality into U2 itself
so that application writers can also write to the system logs where this
is appropriate.
I checked to see if the error messages were being sent to stderr very
early in my 'exploration'. They're not. My initial reaction was "why not?"
We're going to use como with any program that touches GL. It's overkill,
but the SOX auditors don't seem to live in the real world anyway. <gr>
Thanks for all the suggestions and responses.
--
Dave
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
