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

Hi Lennart, Do you have any idea that UBIFS supports writable memory mappings or not? Regards, Karnik Jain On Wed, May 22, 2019 at 12:05 AM Kay One wrote: > Thank you so much for your time. > Let me try changing JFFS2 to UBIFS as another available option to use for > my SOC. > > I would keep y

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

Thank you so much for your time. Let me try changing JFFS2 to UBIFS as another available option to use for my SOC. I would keep you guys posted. Regards, Karnik Jain On Tue, May 21, 2019 at 8:18 PM Lennart Poettering wrote: > On Di, 21.05.19 17:37, Kay One ([email protected]) wrote: > > > Th

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

My server freeze for dbus that begin by freeze for update and upgrade and now that freeze for a dbus works Provenance : Courrier pour Windows 10 De : Dorian ROSSE Envoyé : Tuesday, May 21, 2019 7:41:54 PM À : syste

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

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 parent is systemd lol If somebody know Something about this feeling of dbus-daem

Re: [systemd-devel] Start service after video drivers have been loaded

On Tue, May 21, 2019 at 5:56 PM Mantas Mikulėnas wrote: > On Tue, May 21, 2019 at 1:39 PM Germano Massullo < > [email protected]> wrote: > >> Hello, Fedora / EPEL BOINC comaintainer here. >> On BOINC client we have a problem. On some Linux distributions BOINC >> gets loaded before the vi

Re: [systemd-devel] Start service after video drivers have been loaded

On Tue, May 21, 2019 at 1:39 PM Germano Massullo wrote: > Hello, Fedora / EPEL BOINC comaintainer here. > On BOINC client we have a problem. On some Linux distributions BOINC > gets loaded before the videocard drivers are loaded, so it does not > detect OpenCL/CUDA capabilities. > We cannot use g

Re: [systemd-devel] Start service after video drivers have been loaded

On Di, 21.05.19 12:38, Germano Massullo ([email protected]) wrote: > Hello, Fedora / EPEL BOINC comaintainer here. > On BOINC client we have a problem. On some Linux distributions BOINC > gets loaded before the videocard drivers are loaded, so it does not > detect OpenCL/CUDA capabilities

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

On Di, 21.05.19 17:37, Kay One ([email protected]) wrote: > Thanks for the reply Lennart. > > 1) mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 28, 0) = -1 EINVAL > > (Invalid argument) is the culprit for this error??? Yes. > 2) If YES. Is this JFFS2 MTD file system bug or It's a missing

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

Thanks for the reply Lennart. 1) mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 28, 0) = -1 EINVAL > (Invalid argument) is the culprit for this error??? 2) If YES. Is this JFFS2 MTD file system bug or 3) Is this not considered as systemd bug to support compatibility for such file system? Chec

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

On Di, 21.05.19 16:45, Kay One ([email protected]) wrote: > Hi Lennart, > > Thanks for the reply. > JFFS2 is the file system being used in my case. Also, if I would delete > /var/log/journal directory then these errors are stopping. > Meaning while writing to persistence storage this error is pe

[systemd-devel] Start service after video drivers have been loaded

Hello, Fedora / EPEL BOINC comaintainer here. On BOINC client we have a problem. On some Linux distributions BOINC gets loaded before the videocard drivers are loaded, so it does not detect OpenCL/CUDA capabilities. We cannot use graphical.target as wait condition because there can be headless syst

Re: [systemd-devel] Does "systemctl daemon-reload" discard service information?

Am 21.05.19 um 10:04 schrieb Zbigniew Jędrzejewski-Szmek: > On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote: >> Hi! >> >> I have had the effect that a "systectl status" before and after a >> "daemon-reload" is different, while the service in question wasn't restarted: > > Whenever m

[systemd-devel] Antw: Re: Does "systemctl daemon-reload" discard service information?

>>> Zbigniew Jedrzejewski-Szmek schrieb am 21.05.2019 um 10:04 in Nachricht <[email protected]>: > On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote: >> Hi! >> >> I have had the effect that a "systemctl status" before and after a >> "daemon‑reload" is different, while the

Re: [systemd-devel] Does "systemctl daemon-reload" discard service information?

On Mon, May 20, 2019 at 03:36:28PM +0200, Ulrich Windl wrote: > Hi! > > I have had the effect that a "systectl status" before and after a > "daemon-reload" is different, while the service in question wasn't restarted: Whenever making a report like this, always include the exact systemd version yo

[systemd-devel] Antw: Re: Does "systemctl daemon-reload" discard service information?

>>> Andrei Borzenkov schrieb am 20.05.2019 um 19:07 in Nachricht <[email protected]>: > 20.05.2019 16:36, Ulrich Windl пишет: >> Hi! >> >> I have had the effect that a "systectl status" before and after a >> "daemon-reload" is different, while the service in question