On 12/21/2016 03:15 AM, Per Jessen wrote:
Anton Aylward wrote:
On 12/20/2016 11:59 AM, jdd wrote:
Le 20/12/2016 à 17:36, Carlos E. R. a écrit :
I don't use inn :-)
well, it's the same problem. Don't use standard system log for debug an application. you could as well flood /var/log/messages with this
I think what JDD means, and I agree with him here, is that using syslog for debug is a bit of a kludge.
Well, syslog() has had the LOG_DEBUG level for decades. It may not be exactly "debug" messages, but simply an extensive audit trail.
Maybe I'm a dinosaur but I recall in UNIX 5 and UNIX 6 and UNIX 7 of the early and mid 1970s when there was no syslog. It didn't happen until the 1980s. Think about it: it uses UDP. That needs networking. Adopting syslog for an out of band debug mechanism was and is a kludge. As I said, a proper redirect-able STDDEBUG as part of STDIO would have been the right thing to do. So why didn't it happen? There's a simple reason for this. Back when, there was no non-blocking IO. Eventually, the only way to do non-blocking IO was to make use of the 'select()' call because there was no kernel support for non-blocking IO on a normal STDIO 'read()' as there is now. Today we could implement a non-blocking STDDEBUG channel along with STDIO's STDIN, STDSOUT and STDERR. It might make more sense and in the way that we can use a simple shell redirection of any channel (q.v. man page) it actually offers more flexibility for what Carlos is doing than using syslog as an debug channel. Being able to redirect, filter etc on the command like, tee off STDERR, run it separately through grep ... Oh wait, have you never split an IO channel into a fan-out tree with multiple tee commands? By comparison to what you can do on the command line dynamically compared to having to edit a syslog config file is ...well, I'm a CLI/shell maven of old. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org