A business case, eh? How about "any world-class dbms must have
consistent, comprehensive, and easily configurable error logging." If
U2 doesn't have this then it needs to get it...period!
Every one of us in the applications market know we have to incorporate
basic industry functionality (plus logging) into our application,
otherwise we eventually lose business. Why doesn't this rule apply to
UD? Because they can blow us off and tell us to migrate to UniVerse?
(Perhaps I'm being a little unfair.)
Just IMHO, of course. :-)
Bill
------------------------------------------------------------------------
Doug Averch said the following on 3/15/2010 5:16 PM:
Bill,
That is where in Engineers put them originally. Makes no sense today nor
did
it years ago when I worked there. Also, you have many ways to turn on the
severity of each log as well as getting logs for non-daemons.
I put in a request last year to fix this. No business case, so it was
rejected.
Regards,
Doug
-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett
Sent: Monday, March 15, 2010 4:37 PM
To: U2 Mail List
Subject: [U2] UD - Error Logging
Does anyone know why most of the various UniData logs are in the
"@UDTHOME/bin" directory? Why aren't they in the "@UDTHOME/log"
directory? Maybe there's a @UDTLOG environment variable?
Thanks,
Bill
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
