| From: Giles Orr via talk <[email protected]> | Hugh seems to be correct: I think everything in `dmesg` ends up in the | journal. But what I find interesting is that not everything in | /var/log/systemlog is in the journal.
That doesn't match my (possibly unreliable) model of The Way Things are Supposed to Be. I think: - the syslog facility has been replaced by the journald facility - all the APIs for syslog now go to journald. - That may require rebuilding old packages. (Not changing, just rebuilding, so that the newer libraries get linked.) - I would expect that the new stable debian had rebuilt all packages Any of these beliefs could be wrong. | I was comparing the systemlog | entries, and that's how I concluded CUPS/printer drivers were the | problem. The loading of those modules weren't mentioned in the | journal. In this case, it seems that the information I most needed | (ie. "this is a printer driver problem") came from syslog. So modifying my ealier question, can you see a commonality in the syslog entries just before each crash? | This is a negative test case - ie. I don't know it's solved, and won't | ever be certain. Unless it crashes again, then I know it's not | solved. Ugh. Yeah. And you won't know when it becomes safe to run CUPS again. The best way of gaining confidence would be if a bug fix were released. But you don't even know the bug. It doesn't even sound clear enough to report. --- Post to this mailing list [email protected] Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
