BCLUG wrote:
> One thought might be to disable cups (`journalctl disable --now cups`)
Did you mean 'systemctl disable --now cups' ???
--Bob.
On 2023-10-11 20:06, BCLUG via talk wrote:
Giles Orr via talk wrote on 2023-10-11 15:30:
debugging Linux crashes. The `dmesg` command is useless, as it only
shows the log since the last boot.
The tool for inspecting previous boot logs would be:
## Logs from *previous* boot for `lp` and `cups`:
`journalctl --boot -1 --unit lp --unit cups`
I noticed was this, the only line of consequence about a millisecond
before the reboot: 2023-10-10T11:36:23.839046-04:00 sli7d
systemd-modules-load[399]: Inserted module 'lp'
I don't have a printer, and I hadn't just done a "print-to-PDF" or
anything like that
One thought might be to disable cups (`journalctl disable --now cups`)
and see if that helps (Common Unix Print Service)...
Is it possible that Samba was triggering "lp"-related stuff which was
causing the crash?
That's possible - I can't recall much about samba, but maybe look into
printer(s) is/are being shared and disable that feature.
I suppose I could reboot and select and older kernel and see if that
was stable ... Suggestions on how to better debug this would be most
welcome. Does blacklisting the "lp" module sound like a good idea?
Those also sound like good ideas.
Good luck.
---
Post to this mailing list [email protected]
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
---
Post to this mailing list [email protected]
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
