This is correct, as can be seen in the syslog protocol RFC. This, and other deficiencies in the syslog protocol, is the reason why modern syslog daemons such as rsyslog support enhanced protocols with features such as TCP transport, encryption etc. There was also some effort within the IETF to standardize an improved syslog protocol, … Read more
Alternatively, if you want to keep your syslog intact on one line for parsing, you can just replace the characters when viewing the log. tail -f /var/log/syslog | sed ‘s/#012/\n\t/g’
This is an old question, but neither of the previous two answers are good solutions: The accepted answer doesn’t explain why the disk problem goes away if you fix the underlying system issue (the answer is logrotate), plus your system may keep writing to the logs and fill up your disk before you can even … Read more
When the report points to a program, not a shared library Run addr2line -e myapp 080513b (and repeat for the other instruction pointer values given) to see where the error is happening. Better, get a debug-instrumented build, and reproduce the problem under a debugger such as gdb. If it’s a shared library In the libfoo.so[NNNNNN+YYYY] … Read more
/var/log/system.log You can monitor it easily using tail -f /var/log/system.log See also the “logger” (man logger) and “syslog” (man syslog).
How about less /var/log/syslog?
Change the line to this: handler = SysLogHandler(address=”/dev/log”) This works for me import logging import logging.handlers my_logger = logging.getLogger(‘MyLogger’) my_logger.setLevel(logging.DEBUG) handler = logging.handlers.SysLogHandler(address=”/dev/log”) my_logger.addHandler(handler) my_logger.debug(‘this is debug’) my_logger.critical(‘this is critical’)