Coming from a D3 background, one of the things I REALLY MISS is the RUNTIME-ERRORS file.
If a process has an error in basic runtime, an error is logged. This is especially useful for phantom jobs, or tracking problems onsite when "no one saw anything funny" onscreen - yet we have a log of it! Ross Ferris Stamina Software Visage > Better by Design! >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Craig Bennett >Sent: Thursday, 11 May 2006 2:03 PM >To: u2-users@listserver.u2ug.org >Subject: Re: Fw: [U2] Unidata logging of BASIC Runtime errors > >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. > > > >Craig >------- >u2-users mailing list >u2-users@listserver.u2ug.org >To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
