dmesg shows this:
[ 22.947118] systemd-journald[629]: File
/var/log/journal/26336922e1044e80ae4bd42e1d6b9099/user-1000.journal
corrupted or uncleanly shut down, renaming and replacing.
[ 22.953883] systemd-journald[629]: Creating journal file
/var/log/journal/26336922e1044e80ae4bd42e1d6b9099/u
On Mo, 01.06.20 06:55, Branko (bran...@s5tehnika.net) wrote:
> HI,
>
> I have a problem with and FTDI-based device. It keeps dissapearing and
> reappearing on every 1-2s or so. Nothing in dmesg to indicate failure.
>
> I'm trying to make my way through systemd-udevd, but it's not easy to debug
> t
On So, 31.05.20 14:36, Patrick Dimond (m...@ptrckd.com) wrote:
> Hi,
> I was reading the documentation for systemd.resource-control and came
> across this sentence under accounting settings.
>
> "Note that turning on memory accounting for one unit will also
> implicitly turn it on for all units co
HI,
I have a problem with and FTDI-based device. It keeps dissapearing and
reappearing on every 1-2s or so. Nothing in dmesg to indicate failure.
I'm trying to make my way through systemd-udevd, but it's not easy to
debug things there ( neither is classic udev BTW).
udevadm monitor -u shows
