[systemd-devel] pid 1 memlock setting configurable?

Hi all, I couldn't find it with google, and before digging in the code just a quick question. Probably someone knows it in the top of h(is|er) head... It seems that systemd drops rlimit_memlock on startup. Correct? And if so, is it configurable? Explanation for the question: In an unprivileged

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

I enabled core dump I follown this link : https://linux-audit.com/understand-and-configure-core-dumps-work-on-linux/ But do this answer of this command line are good ? : cat /proc/sys/kernel/core_pattern /var/crash/core.%u.%e.%p Thank you in advance to follow the problem, Regards. Dori

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

No It failed : ulimit -S -c dbus-daemon -bash: ulimit: dbus-daemon: invalid number Provenance : Courrier pour Windows 10 De : Ulrich Windl Envoyé : Wednesday, May 22, 2019 3:17:32 PM À : Dorian ROSSE; Lennart

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

I enabled core dump for dbus Provenance : Courrier pour Windows 10 De : Ulrich Windl Envoyé : Wednesday, May 22, 2019 3:17:32 PM À : Dorian ROSSE; Lennart Poettering Cc : [email protected] O

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

Could it be that dbus dies (unexpectedly), and systemd needs dbus to work? Maybe enabling coredumps could help finding out why dbus quits. Regards, Ulrich >>> Dorian ROSSE schrieb am 22.05.2019 um 14:03 in Nachricht > I have agains dbus‑daemon shown as zombie as Following : > > ps aux |grep "

Re: [systemd-devel] [PATCH] man: systemd-nspawn: Update syntax to launch an image

On Mo, 20.05.19 17:08, Kashyap Chamarthy ([email protected]) wrote: > To access a shell on a disk image, the man page on Fedora-29 says to > run: `systemd-nspawn -M Fedora-Cloud-Base-28-1.1.x86_64.raw`. Let's > try. > > List existing images: > > $> machinectl list-images | awk '{print $1,$2

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

I have agains dbus-daemon shown as zombie as Following : ps aux |grep "defunct" root 13349 0.0 0.0 0 0 ?Zs 12:00 0:00 [dbus-daemon] Regards. Dorian ROSSE. Provenance : Courrier pour Windows 10 __

Re: [systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

I launch the command line adviced strace -p 1 strace -p 1 strace: Process 1 attached ppoll([{fd=22, events=POLLIN}], 1, {tv_sec=53, tv_nsec=119912101}, NULL, 8 Why I should search a coredump ? What I must do now ? Now I have my system frozen for update and upgrade :’( , Thank you for your t

Re: [systemd-devel] Antw: Re: systemd-tmpfiles-setup.service failed due to LDAP resolving

On Wed, May 22, 2019 at 12:52 PM Ulrich Windl < [email protected]> wrote: > >>> Lennart Poettering schrieb am 22.05.2019 um > 10:30 > in > Nachricht <20190522083028.GA30001@gardel-login>: > > On Mi, 22.05.19 10:02, Ulrich Windl ([email protected]‑regensburg.de) > wrote: > > > >>

Re: [systemd-devel] systemd-tmpfiles-setup.service failed due to LDAP resolving

On Wed, May 22, 2019 at 11:30 AM Lennart Poettering wrote: > On Mi, 22.05.19 10:02, Ulrich Windl ([email protected]) > wrote: > > > Hi! > > > > Obviously the owner of a temporary directory cannot be an LDAP user: > > system users should really not be located on LDAP: > > > https:/

[systemd-devel] Antw: Re: systemd-tmpfiles-setup.service failed due to LDAP resolving

>>> Lennart Poettering schrieb am 22.05.2019 um 10:30 in Nachricht <20190522083028.GA30001@gardel-login>: > On Mi, 22.05.19 10:02, Ulrich Windl ([email protected]‑regensburg.de) wrote: > >> Hi! >> >> Obviously the owner of a temporary directory cannot be an LDAP user: > > system users should r

Re: [systemd-devel] interacting with logind to detect user idle time

Il giorno mer 22 mag 2019 alle ore 11:41 Mantas Mikulėnas ha scritto: > On Wed, May 22, 2019, 12:37 Germano Massullo > wrote: >> Second question: perhaps can be useful if I start a topic in GNOME / >> KDE Plasma development mailing lists asking them to make patches that >> will let systemd-login

Re: [systemd-devel] interacting with logind to detect user idle time

On Wed, May 22, 2019, 12:37 Germano Massullo wrote: > Il giorno mer 22 mag 2019 alle ore 11:17 Mantas Mikulėnas > ha scritto: > > If your program is already X11-based, you could use the screensaver > protocol to get idle status and forward it to logind. > > BOINC client is just a service, and it

Re: [systemd-devel] interacting with logind to detect user idle time

Il giorno mer 22 mag 2019 alle ore 11:17 Mantas Mikulėnas ha scritto: > If your program is already X11-based, you could use the screensaver protocol > to get idle status and forward it to logind. BOINC client is just a service, and it runs on machines that can run X11, Wayland, or no graphical s

Re: [systemd-devel] interacting with logind to detect user idle time

On Wed, May 22, 2019, 12:13 Germano Massullo wrote: > Good day. > I have noticed that on many Linux distributions with different desktop > environments, the properties > IdleSinceHint > IdleSinceHintMonotonic > are always equal to zero. This happens even if you try to use a sleep > in order to si

Re: [systemd-devel] interacting with logind to detect user idle time

Good day. I have noticed that on many Linux distributions with different desktop environments, the properties IdleSinceHint IdleSinceHintMonotonic are always equal to zero. This happens even if you try to use a sleep in order to simulate a kind of user inactivity. What is this happening? I have wri

[systemd-devel] Antw: Re: Failed to open system journal: Invalid argument

>>> Lennart Poettering schrieb am 22.05.2019 um 10:34 >>> in Nachricht <20190522083459.GC30001@gardel-login>: > On Mi, 22.05.19 01:03, Kay One ([email protected]) wrote: > >> Hi Lennart, >> >> Do you have any idea that UBIFS supports writable memory mappings or >> not? > > No idea, sorry! >

[systemd-devel] Antw: Re: dbus-daemon keep shown as zombie process why ?

>>> Lennart Poettering schrieb am 22.05.2019 um 10:32 in Nachricht <20190522083211.GB30001@gardel-login>: > On Di, 21.05.19 17:41, Dorian ROSSE ([email protected]) wrote: > >> Hello everybody, >> >> >> I know this isn’t a bug or a systemd problems but It keeps the >> system in thought of dbu

Re: [systemd-devel] Failed to open system journal: Invalid argument

On Mi, 22.05.19 01:03, Kay One ([email protected]) wrote: > Hi Lennart, > > Do you have any idea that UBIFS supports writable memory mappings or > not? No idea, sorry! This suggests that UBIFS treats mmap like any other fs would, and thus probably also supports mmap() just fine in writable mod

Re: [systemd-devel] dbus-daemon keep shown as zombie process why ?

On Di, 21.05.19 17:41, Dorian ROSSE ([email protected]) wrote: > Hello everybody, > > > I know this isn’t a bug or a systemd problems but It keeps the > system in thought of dbus-daemon should be a zombie process but my > web page about zombie process say I should kill the parent but the > pa

Re: [systemd-devel] systemd-tmpfiles-setup.service failed due to LDAP resolving

On Mi, 22.05.19 10:02, Ulrich Windl ([email protected]) wrote: > Hi! > > Obviously the owner of a temporary directory cannot be an LDAP user: system users should really not be located on LDAP: https://systemd.io/UIDS-GIDS.html#notes-on-resolvability-of-user-and-group-names > May

[systemd-devel] systemd-tmpfiles-setup.service failed due to LDAP resolving

Hi! Obviously the owner of a temporary directory cannot be an LDAP user: # systemctl status systemd-tmpfiles-setup -l ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)