Re: [systemd-devel] Dropping core with Systemd.
Am Mon, 15 May 2017 11:54:08 -0400 schrieb Steve Dickson : > Hello, > > I want rpcbind to drop core so I can debug > something but systemd keeps getting in the way > > systemd: rpcbind.service: Main process exited, code=killed, > status=6/ABRT audit: ANOM_ABEND auid=4294967295 uid=32 gid=32 > ses=4294967295 subj=system_u:system_r:rpcbind_t:s0 pid=2787 > comm="rpcbind" exe="/usr/bin/rpcbind" sig=6 systemd: rpcbind.service: > Unit entered failed state. audit: SERVICE_STOP pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" > hostname=? addr=? terminal=? res=failed' systemd: rpcbind.service: > Failed with result 'signal'. systemd: Starting RPC Bind... systemd: > Started RPC Bind. > > How do I stop systemd from restarting rpcbind and allowing > the process to drop core? > > Note, this problem only happens when systemd starts rpcbind > and ypbind so I need systemd to start the processes. Usually you should find it listed when you run "coredumpctl". For this to work, sysctl should have: kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e kernel.core_pipe_limit = 0 kernel.core_uses_pid = 1 This should be default with a default systemd installation. You may need to mask/unmask one sysctl file. Check /usr/lib/sysctl.d/50-coredump.conf. -- Regards, Kai Replies to list-only preferred. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Dropping core with Systemd.
Hello, I want rpcbind to drop core so I can debug something but systemd keeps getting in the way systemd: rpcbind.service: Main process exited, code=killed, status=6/ABRT audit: ANOM_ABEND auid=4294967295 uid=32 gid=32 ses=4294967295 subj=system_u:system_r:rpcbind_t:s0 pid=2787 comm="rpcbind" exe="/usr/bin/rpcbind" sig=6 systemd: rpcbind.service: Unit entered failed state. audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpcbind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' systemd: rpcbind.service: Failed with result 'signal'. systemd: Starting RPC Bind... systemd: Started RPC Bind. How do I stop systemd from restarting rpcbind and allowing the process to drop core? Note, this problem only happens when systemd starts rpcbind and ypbind so I need systemd to start the processes. tia, steved. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd user session manager
Hi, I'm Ronan from Iot.bzh team and I'm currently working on AGL project. https://www.automotivelinux.org/ (AGL is an embedded system). For the AGL project, I use systemd as a user login session manager. Throw a service "*agl-user-session@.service"* [Service] User=%i PAMName=agl-user-session // (2) ExecStart=-/bin/sleep 2147483648 // (1) KillMode=mixed Delegate=yes TasksMax=infinity (1): We need to have a process up so, as a first steep, I use a "sleep". (2): we can't use "systemd-user" for the PAMName. PAMName "systemd-user" is hardcoded here: ./src/login/pam_systemd.c:267 And we want logind create a session for us, this is why we use a custom PAMName "agl-user-session" Question: 1) Can you confirm, is it a good way to use systemd? 2) Does systemd have a alternative? Regards, Ronan Le Martret [IoT.bzh] ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
