- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Frist, snecod, TURD
Admin
Ahhhh, but this gives you errorLogFacility and logID parameters, perhaps dynamically chosen/generated! That's something you can achieve with awk in some simple ways, which should be available since they are invoking
/usr/binas a path...Admin
I've just been dealing with something in a similar vein. We've got an application that does a near-realtime replication of Progress data into a SQL database (to make reporting and PowerBI stuff easier).
That application writes to a log file when it performs a sync. It also writes to another log file that that a log message about the sync was written. So we've essentially got logging about logging.
I'm at a loss to understand the design decision that lead to someone writing log files about the success or failures of other logs files being written. It's log files all the way down.