Team,
I have compiled my linux kernel using 'allnoconfig' and added back
in all the kernel options that have been documented as necessary for
systemd. I'm still getting an error. It fails trying to start
[email protected], and it is related to PAM somehow.
Here is the debug log:
Feb 14 23:48:57 in
On Wed, Feb 14, 2018 at 1:38 AM, Lennart Poettering
wrote:
>
> That all said, I think we should really try to make systemd work with
> your usecase directly and natively, i.e. add enough flexibility to
> systemd so that you don't have to wrap it in such a "foreign" prefix
> cgroup to do what you w
On Mi, 14.02.18 06:42, P.R.Dinesh ([email protected]) wrote:
> I am interesting in getting some statistics information from journal, for
> eg.,
> 1) number of logs
> 2) number of logs per severity
> 3) number of logs per daemon
I presume you mean "log records" when you write "logs", right?
Suc
On Di, 13.02.18 17:06, Josh Snyder ([email protected]) wrote:
> I've tested against both legacy and unified cgroup hierarchies. The
> functionality to detect the current cgroups and nest processes underneath them
> appears to be in manager_setup_cgroup (src/core/cgroup.c:2033). My question
> for
