[systemd-devel] "systemd-nspawn -b ..." works, "machinectl start" fails with "ethtool ioctl" related errors

2017-01-24 Thread Germano Massullo
Hi everybody. I am used to create and use systemd-nspawn containers (on Fedora 25) with the following few lines of bash # lvcreate --name test -L 200G vg_machines # mkfs.ext4 /dev/vg_machines/test # mkdir /var/lib/machines/test # mount /dev/vg_machines/test

Re: [systemd-devel] "systemd-nspawn -b ..." works, "machinectl start" fails with "ethtool ioctl" related errors

2017-01-24 Thread Germano Massullo
It looks like the problem is systemd-networkd disabled on both host machine and container. Thanks to Francesco Frassinelli for the hint ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] "systemd-nspawn -b ..." works, "machinectl start" fails with "ethtool ioctl" related errors

2017-01-24 Thread Germano Massullo
Errata corrige: # cat /etc/systemd/nspawn/theta-1.nspawn is # cat /etc/systemd/nspawn/test.nspawn ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] "systemd-nspawn -b ..." works, "machinectl start" fails with "ethtool ioctl" related errors

2017-01-28 Thread Germano Massullo
Days ago I found out the real cause of this problem: (SELinux bugreport) machinectl user experience is completely broken https://bugzilla.redhat.com/show_bug.cgi?id=1416540 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

Re: [systemd-devel] logind + GDbus API

2018-10-19 Thread Germano Massullo
Il giorno mer 17 ott 2018 alle ore 10:56 Lennart Poettering ha scritto: > > On Mi, 17.10.18 09:50, Germano Massullo (germano.massu...@gmail.com) wrote: > > > Good day, I planned to write a tiny software for testing purposes that > > will use GDbus API to interact with login

[systemd-devel] logind + GDbus API

2018-10-17 Thread Germano Massullo
Good day, I planned to write a tiny software for testing purposes that will use GDbus API to interact with logind, in order to detect user idle time. I am still studying GDbus API, and I am also looking for some very good example of GDbus API + logind usage, in order to learn best practices in

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

2019-05-17 Thread Germano Massullo
Perfect, thank you very much! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

2019-06-14 Thread Germano Massullo
I have two different options at the moment, and I would like to ask you for a feedback. A file /usr/lib/udev/rules.d/01-boinc-gpu-plugged.rules containing ACTION=="add", SUBSYSTEM=="drm", RUN+=systemctl --no-block restart boinc-client.service should restart BOINC client when a new DRM device

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

2019-06-09 Thread Germano Massullo
Il giorno mar 21 mag 2019 alle ore 16:59 Mantas Mikulėnas ha scritto: > Actually, maybe having udev trigger BOINC startup would be a good option? > After all that's how BlueZ already works -- it doesn't go in > multi-user.target, it has WantedBy=bluetooth.target and there's an udev rule > that

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

2019-06-17 Thread Germano Massullo
Il giorno lun 17 giu 2019 alle ore 11:07 Lennart Poettering ha scritto: > > On So, 09.06.19 19:45, Germano Massullo (germano.massu...@gmail.com) wrote: > > > Il giorno mar 21 mag 2019 alle ore 16:59 Mantas Mikulėnas > > ha scritto: > Actually, maybe having udev > >

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

2019-05-14 Thread Germano Massullo
Il giorno lun 13 mag 2019 alle ore 10:00 Lennart Poettering ha scritto: > Note that it only works correctly on desktops that support it. Thank you for your reply. Why does it work only on desktop environments that support it? I believed that it provides idle infos to the D.E. not viceversa

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

2019-05-22 Thread Germano Massullo
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 &

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

2019-05-22 Thread Germano Massullo
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

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

2019-05-22 Thread Germano Massullo
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

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

2019-05-23 Thread Germano Massullo
I have sent the following message to various desktop environment mailing lists SUBJECT: Proposal: passing user idle time to systemd-logind KDE Plasma: https://mail.kde.org/pipermail/plasma-devel/2019-May/098194.html GNOME: https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00088.html

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

2019-05-21 Thread Germano Massullo
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

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

2019-05-16 Thread Germano Massullo
To do practise I am using NetworkManager example [1] All macros passed as arguments to functions g_dbus_proxy_call_sync g_dbus_proxy_new_for_bus_sync are implemented at [2]. Is there an equivalent of [2] for logind? I made a quick search into systemd repository [3] but I am getting too many

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

2019-05-08 Thread Germano Massullo
Hi, I am doing some practice with writing software using GDBus API. I need it to implement on BOINC client, user(s) idle time detection by retrieving such info from logind. In order to retrieve user idle time I was thinking of using the property IdleSinceHint. What do you think about? Best

[systemd-devel] emergency shutdown, don't wait for timeouts

2020-12-27 Thread Germano Massullo
Good day, I recently joined apcupsd (APC UPS Power Control Daemon) package maintainers on Fedora/CentOS/RHEL. After a power failure, apcupsd shuts down the system with a command almost identical to shutdown -h -H now Usually when you normally shutdown your system, you may notice certain services

Re: [systemd-devel] emergency shutdown, don't wait for timeouts

2020-12-28 Thread Germano Massullo
Il 27/12/20 15:40, Andrei Borzenkov ha scritto: > 27.12.2020 17:00, Reindl Harald пишет: >> >> Am 27.12.20 um 14:43 schrieb Andrei Borzenkov: >>> 27.12.2020 16:26, Germano Massullo пишет: >>>> Good day, I recently joined apcupsd (APC UPS Power Control Daemon

Re: [systemd-devel] emergency shutdown, don't wait for timeouts

2020-12-28 Thread Germano Massullo
Il 27/12/20 15:00, Reindl Harald ha scritto: > > > Am 27.12.20 um 14:43 schrieb Andrei Borzenkov: >> 27.12.2020 16:26, Germano Massullo пишет: >>> Good day, I recently joined apcupsd (APC UPS Power Control Daemon) >>> package maintainers on Fedora/CentOS/RHEL. &