Quote:
Originally Posted by
theKbStockpiler
What is the technical term for writing the code that sources the log files like klogd and syslogd?
You mean, writes the log files?
How about "error logging"?
Quote:
I run my own code that oversees how my programs intentions panned out, then I use a logger command correct?
Depends what you're trying to do.
Quote:
What system resources aide in determining if an error has occurred? Proc, Trace , OOP events and what else?
Generally none of the above. Unless something goes
seriously wrong like a segfault, generally only your program knows if anything's going wrong.
An 'OOP event' in particular isn't a real thing. It's a programming method/buzzword. Object-oriented programs still deal with the same things.
In the end, checking for errors means checking if any data you receive makes sense, and checking if system calls you make succeed or not.
Quote:
I expect to find a lot of intentional documents on this subject but it looks like everyone must just wing it.
It sounds like you're reading papers describing what should be done but not how.
What, exactly, are you trying to do here? It sounds almost like you've been handed a list of substanceless buzzwords from on high and been told to obey them.