But how to check what is happening? and I am still not sure why my normal laptop with systemd works properly and starts journald.
W dniu 14.08.2016 o 06:56, Andrei Borzenkov pisze: > 14.08.2016 04:58, Michał Zegan пишет: >> Hello. I have installed systemd version 231 from arch repos. actually it >> is systemd-selinux from aur. now, the problem: >> the system boots. but some services fail to start, notably >> systemd-journald and systemd-networkd, not sure if others fail too. >> When checking what happened using dmesg as journald does not work, I get >> that the control process received signal 31, marked sigsys. no explanation. >> I have normal systemd 231 on my laptop, and it works with journal and >> all. In addition, running processes normally on this pc where it does >> not work does not kill them with signal sigsys. > > SIGSYS is used by seccomp to kill process with SECCOMP_RET_KILL. So it > looks like some too restrictive filters are in effect. > >> Does anyone know or suspect what may be the cause? My kernel has a >> heavily modified configuration, and I just upgraded from 4.6 to 4.7 and >> configured using make oldconfig. >> >> >> >> _______________________________________________ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
