Re: [systemd-devel] systemd-python at pypi
On 21/04/2020 19:35, Anders Buch wrote: > Hello, > > Are there any plans to update the pypi version of python-sytemd here: > https://pypi.org/project/systemd-python/ > > The following results in errors on Ubuntu 18.04 with latest python3.8 > packages installed (as well as libsystemd-dev and python3-systemd): > > python3.8 -m venv systemd_test > . systemd_test/bin/activate > pip install systemd-python > > The error is: > > systemd/_journal.c:21:10: fatal error: Python.h: No such file or directory > #include This error is due to the fact that you do not have the necessary development files to compile extensions for python3.8. I guess you need to `apt-get install python3.8-dev`. Cheers, Dan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-python at pypi
Hello, Are there any plans to update the pypi version of python-sytemd here: https://pypi.org/project/systemd-python/ The following results in errors on Ubuntu 18.04 with latest python3.8 packages installed (as well as libsystemd-dev and python3-systemd): python3.8 -m venv systemd_test . systemd_test/bin/activate pip install systemd-python The error is: systemd/_journal.c:21:10: fatal error: Python.h: No such file or directory #include I can provide more output, but I expect this is easy to reproduce. This issue means that I can only use python-systemd with the system version of Python (which is 3.6, so doesn't support many asyncio features). Thanks in advance for any comments! Anders ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Not able to get valgrind profiling output after starting systemd-udevd.service through valgrind.
On Di, 21.04.20 20:52, Amit anand (amit.ta...@gmail.com) wrote: > Apr 21 16:27:16 [xxx] valgrind[4252]: valgrind: m_ume.c: can't open > interpreter There's something not right with the ELF interpretor in your binaries. maybe some cross-building fuck-up? It's probably best to ping the valgrind community about that, it has nothing to do with systemd. Other people ran into the same error: https://sourceforge.net/p/valgrind/mailman/message/35008834/ maybe googling further might help you. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Not able to get valgrind profiling output after starting systemd-udevd.service through valgrind.
Hi, Tried to run debug-symbol enabled systemd-udevd through valgrind. root@[xxx]:/var/opt# vi /etc/systemd/system/.../systemd-udevd.service ExecStart=/usr/bin/valgrind --tool=memcheck /lib/systemd/.debug/systemd-udevd // Modified to run debug-symbol enabled systemd.udevd binary through valgrind. root@[xxx]:/var/opt# systemctl daemon-reload Not able to run debug-symbol enabled systemd-udevd through valgrind. Below error message: root@[xxx]:/var/opt# systemctl restart systemd-udevd Job for systemd-udevd.service failed because the control process exited with error code. See "systemctl status systemd-udevd.service" and "journalctl -xe" for details systemctl status -n1000 systemd-udevd.service [[0;1;31m●[[0m systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/lib/systemd/system/systemd-udevd.service; enabled; vendor preset: enabled) Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2020-04-21 16:27:16 UTC; 40s ago Docs: man:systemd-udevd.service(8) man:udev(7) Process: 4252 ExecStart=/usr/bin/valgrind --tool=memcheck /lib/systemd/.debug/systemd-udevd [[0;1;31m(code=exited, status=1/FAILURE)[[0m Main PID: 4252 (code=exited, status=1/FAILURE) Apr 21 16:27:16 [xxx] valgrind[4252]: valgrind: m_ume.c: can't open interpreter Apr 21 16:27:16 [xxx] systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39msystemd-udevd.service: Failed with result 'exit-code'.[[0m Apr 21 16:27:16 [xxx] systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start udev Kernel Device Manager.[[0m Kindly let me know if anything missed. Regards, Amit On Thu, Apr 16, 2020 at 7:26 PM Lennart Poettering wrote: > On Di, 14.04.20 20:00, Amit anand (amit.ta...@gmail.com) wrote: > > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ??? > > (in /lib/ld-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B: > > _dl_catch_exception (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012789: ??? > > (in /lib/ld-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC2DC: ??? > > (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B: > > _dl_catch_exception (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCCFE: > > _dl_catch_error (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC3A6: ??? > > (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC436: > > __libc_dlopen_mode (in /lib/libc-2.27.so) > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179== Address 0x650b1c0 is > > 16 bytes after a block of size 32 in arena "client" > > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179== > > To be truly useful you need to enable debug symbols in your builds, so > that valgrind can show you something for useful than pointer values. > > Lennart > > -- > Lennart Poettering, Berlin > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd autofs in RH 7
Am Dienstag, den 21.04.2020, 14:33 + schrieb Wieschke, Thomas: > Hi, > thanks fort he quick response. After having a first look at the man pages, I > mentioned that I would have a choice between > a fstab based solution or a unit file based one, right? > Because I have a mix of ~ 10 different Mounts (CIFS, NFS) /workdir/in, > /workdir/out, /workdir/bla, /workdir/send ... > I have a tendency to fstab because it seems better manageable or what would > you suggest? > > BR > Thomas Hi Thomas, using the fstab is the preferred interface. BR Silvio ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd autofs in RH 7
Hi, thanks fort he quick response. After having a first look at the man pages, I mentioned that I would have a choice between a fstab based solution or a unit file based one, right? Because I have a mix of ~ 10 different Mounts (CIFS, NFS) /workdir/in, /workdir/out, /workdir/bla, /workdir/send ... I have a tendency to fstab because it seems better manageable or what would you suggest? BR Thomas NOVENTI Health SE | Tomannweg 6 | 81673 München Telefon +49 89 43184-153 | thomas.wiesc...@noventi.de | www.noventi.de Vorstand: Dr. Hermann Sommer (Vorsitzender) | Dr. Sven Jansen | Victor J. Castro Erweiterter Vorstand: Sven Bertram (CTO) | Dr. Verena Heeschen (CHRO) | Dr. Silvio Kusche (CMO) | Dr. Sven Simons (CCIO) | Björn Zeien (CSO) Aufsichtsratsvorsitzender: Uwe Geiß Sitz der Gesellschaft: München, Registergericht München HRB 234740 | USt-IdNr.: DE314305075 -Ursprüngliche Nachricht- Von: systemd-devel Im Auftrag von Silvio Knizek Gesendet: Dienstag, 21. April 2020 15:46 An: systemd-devel@lists.freedesktop.org Betreff: Re: [systemd-devel] systemd autofs in RH 7 Am Dienstag, den 21.04.2020, 13:26 + schrieb Wieschke, Thomas: > Hi, > I hope someone can help with the following case. > > I'm writing on a RH 7 system to an automounted FS and get an disruption > because systemd (??) is, > besides working in this directory, obviously trying an umount in the > background. > The umount doesn't work because the FS is in use (returned busy), but the > start/stop of autofs is > nevertheless done and leads to a disruption: > > Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on > demand... > -- Subject: Unit autofs.service has begun shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has begun shutting down. > Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount > Apr 21 12:02:20 server1 systemd[1]: Stopped Automounts filesystems on demand. > -- Subject: Unit autofs.service has finished shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has finished shutting down. > Apr 21 12:02:20 server1 systemd[1]: Starting Automounts filesystems on > demand... > -- Subject: Unit autofs.service has begun start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has begun starting up. > Apr 21 12:02:20 server1 systemd[1]: Started Automounts filesystems on demand. > -- Subject: Unit autofs.service has finished start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has finished starting up. > -- > -- The start-up result is done. > > Finally I tried to prevent any umount by changing in /etc/sysconfig/autofs > #OPTIONS="" to OPTIONS="-timeout=0" > > And I tried to add in /etc/auto.master at end of line --timeout=0 (/workdir > /etc/auto.workdir --timeout=0) > > But besides this values there is an automatic restart every 30min > > Apr 21 13:34:41 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 13:34:42 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 13:34:42 server1 systemd: Started Automounts filesystems on demand. > Apr 21 14:04:42 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 14:04:42 server1 systemd: Stopped Automounts filesystems on demand. > Apr 21 14:04:42 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 14:04:42 server1 systemd: Started Automounts filesystems on demand. > Apr 21 14:34:42 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 14:34:42 server1 automount[11019]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount > Apr 21 14:34:44 server1 systemd: Stopped Automounts filesystems on demand. > Apr 21 14:34:44 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 14:34:44 server1 systemd: Started Automounts filesystems on demand. > > Switching back to RH 6 doesn't show this problem. > > Any suggestions? > > Thanks in advance > > Best regards > Thomas Hi Thomas, don't use autofs, but systemd.automount for this. It does exactly what you want, but in the context of systemd. See man:systemd.automount for more information. BR Silvio ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd autofs in RH 7
Am 21.04.20 um 15:26 Uhr schrieb Wieschke, Thomas: > I'm writing on a RH 7 system to an automounted FS and get an disruption > because systemd (??) is, > besides working in this directory, obviously trying an umount in the > background. > The umount doesn't work because the FS is in use (returned busy), but the > start/stop of autofs is > nevertheless done and leads to a disruption: This sound like a bug in util-linux which was fixed upstream recently: https://github.com/karelzak/util-linux/commit/7065cc0e5312cafc5ae3e4c342f78f264300fb5f Cheers, Ignaz ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd autofs in RH 7
On Di, 21.04.20 13:26, Wieschke, Thomas (thomas.wiesc...@noventi.de) wrote: > > Hi, > I hope someone can help with the following case. > > I'm writing on a RH 7 system to an automounted FS and get an disruption > because systemd (??) is, > besides working in this directory, obviously trying an umount in the > background. > The umount doesn't work because the FS is in use (returned busy), but the > start/stop of autofs is > nevertheless done and leads to a disruption: Something appears to stop and restart your autofs service every half an our. try to figure out why. > > Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on > demand... > -- Subject: Unit autofs.service has begun shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has begun shutting down. > Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: > ask umount returned busy /vsaabrmount This is a message from your automount service, not from systemd. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: [EXT] Re: systemd autofs in RH 7
>>> Silvio Knizek schrieb am 21.04.2020 um 15:45 in Nachricht <24197_1587476741_5E9EF905_24197_143_1_61f65bea728c37e386b1212f4f282aefc193ab0c. a...@gmx.net>: > Am Dienstag, den 21.04.2020, 13:26 + schrieb Wieschke, Thomas: >> Hi, >> I hope someone can help with the following case. >> >> I'm writing on a RH 7 system to an automounted FS and get an disruption > because systemd (??) is, >> besides working in this directory, obviously trying an umount in the > background. >> The umount doesn't work because the FS is in use (returned busy), but the > start/stop of autofs is >> nevertheless done and leads to a disruption: >> >> Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on > demand... >> ‑‑ Subject: Unit autofs.service has begun shutting down >> ‑‑ Defined‑By: systemd >> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel >> ‑‑ >> ‑‑ Unit autofs.service has begun shutting down. >> Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount >> Apr 21 12:02:20 server1 systemd[1]: Stopped Automounts filesystems on > demand. >> ‑‑ Subject: Unit autofs.service has finished shutting down >> ‑‑ Defined‑By: systemd >> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel >> ‑‑ >> ‑‑ Unit autofs.service has finished shutting down. >> Apr 21 12:02:20 server1 systemd[1]: Starting Automounts filesystems on > demand... >> ‑‑ Subject: Unit autofs.service has begun start‑up >> ‑‑ Defined‑By: systemd >> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel >> ‑‑ >> ‑‑ Unit autofs.service has begun starting up. >> Apr 21 12:02:20 server1 systemd[1]: Started Automounts filesystems on > demand. >> ‑‑ Subject: Unit autofs.service has finished start‑up >> ‑‑ Defined‑By: systemd >> ‑‑ Support: http://lists.freedesktop.org/mailman/listinfo/systemd‑devel >> ‑‑ >> ‑‑ Unit autofs.service has finished starting up. >> ‑‑ >> ‑‑ The start‑up result is done. >> >> Finally I tried to prevent any umount by changing in /etc/sysconfig/autofs > #OPTIONS="" to OPTIONS="‑timeout=0" >> >> And I tried to add in /etc/auto.master at end of line ‑‑timeout=0 (/workdir > /etc/auto.workdir ‑‑timeout=0) >> >> But besides this values there is an automatic restart every 30min >> >> Apr 21 13:34:41 server1 systemd: Stopping Automounts filesystems on > demand... >> Apr 21 13:34:42 server1 systemd: Starting Automounts filesystems on > demand... >> Apr 21 13:34:42 server1 systemd: Started Automounts filesystems on demand. >> Apr 21 14:04:42 server1 systemd: Stopping Automounts filesystems on > demand... >> Apr 21 14:04:42 server1 systemd: Stopped Automounts filesystems on demand. >> Apr 21 14:04:42 server1 systemd: Starting Automounts filesystems on > demand... >> Apr 21 14:04:42 server1 systemd: Started Automounts filesystems on demand. >> Apr 21 14:34:42 server1 systemd: Stopping Automounts filesystems on > demand... >> Apr 21 14:34:42 server1 automount[11019]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount >> Apr 21 14:34:44 server1 systemd: Stopped Automounts filesystems on demand. >> Apr 21 14:34:44 server1 systemd: Starting Automounts filesystems on > demand... >> Apr 21 14:34:44 server1 systemd: Started Automounts filesystems on demand. >> >> Switching back to RH 6 doesn't show this problem. >> >> Any suggestions? >> >> Thanks in advance >> >> Best regards >> Thomas > > Hi Thomas, > > don't use autofs, but systemd.automount for this. It does exactly what > you want, but in the context of systemd. See man:systemd.automount for > more information. I wonder when we can boot systemd and run the kernel as an optional module ;-) I guess the bootloader systemd.supergrub is almost complete meanwhile... > > BR > Silvio > > ___ > systemd‑devel mailing list > systemd‑de...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd‑devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd autofs in RH 7
Am Dienstag, den 21.04.2020, 13:26 + schrieb Wieschke, Thomas: > Hi, > I hope someone can help with the following case. > > I'm writing on a RH 7 system to an automounted FS and get an disruption > because systemd (??) is, > besides working in this directory, obviously trying an umount in the > background. > The umount doesn't work because the FS is in use (returned busy), but the > start/stop of autofs is > nevertheless done and leads to a disruption: > > Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on > demand... > -- Subject: Unit autofs.service has begun shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has begun shutting down. > Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount > Apr 21 12:02:20 server1 systemd[1]: Stopped Automounts filesystems on demand. > -- Subject: Unit autofs.service has finished shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has finished shutting down. > Apr 21 12:02:20 server1 systemd[1]: Starting Automounts filesystems on > demand... > -- Subject: Unit autofs.service has begun start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has begun starting up. > Apr 21 12:02:20 server1 systemd[1]: Started Automounts filesystems on demand. > -- Subject: Unit autofs.service has finished start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit autofs.service has finished starting up. > -- > -- The start-up result is done. > > Finally I tried to prevent any umount by changing in /etc/sysconfig/autofs > #OPTIONS="" to OPTIONS="-timeout=0" > > And I tried to add in /etc/auto.master at end of line --timeout=0 (/workdir > /etc/auto.workdir --timeout=0) > > But besides this values there is an automatic restart every 30min > > Apr 21 13:34:41 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 13:34:42 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 13:34:42 server1 systemd: Started Automounts filesystems on demand. > Apr 21 14:04:42 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 14:04:42 server1 systemd: Stopped Automounts filesystems on demand. > Apr 21 14:04:42 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 14:04:42 server1 systemd: Started Automounts filesystems on demand. > Apr 21 14:34:42 server1 systemd: Stopping Automounts filesystems on demand... > Apr 21 14:34:42 server1 automount[11019]: umount_autofs_indirect: ask umount > returned busy /vsaabrmount > Apr 21 14:34:44 server1 systemd: Stopped Automounts filesystems on demand. > Apr 21 14:34:44 server1 systemd: Starting Automounts filesystems on demand... > Apr 21 14:34:44 server1 systemd: Started Automounts filesystems on demand. > > Switching back to RH 6 doesn't show this problem. > > Any suggestions? > > Thanks in advance > > Best regards > Thomas Hi Thomas, don't use autofs, but systemd.automount for this. It does exactly what you want, but in the context of systemd. See man:systemd.automount for more information. BR Silvio ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd autofs in RH 7
Hi, I hope someone can help with the following case. I'm writing on a RH 7 system to an automounted FS and get an disruption because systemd (??) is, besides working in this directory, obviously trying an umount in the background. The umount doesn't work because the FS is in use (returned busy), but the start/stop of autofs is nevertheless done and leads to a disruption: Apr 21 12:02:18 server1 systemd[1]: Stopping Automounts filesystems on demand... -- Subject: Unit autofs.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit autofs.service has begun shutting down. Apr 21 12:02:19 server1 automount[22213]: umount_autofs_indirect: ask umount returned busy /vsaabrmount Apr 21 12:02:20 server1 systemd[1]: Stopped Automounts filesystems on demand. -- Subject: Unit autofs.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit autofs.service has finished shutting down. Apr 21 12:02:20 server1 systemd[1]: Starting Automounts filesystems on demand... -- Subject: Unit autofs.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit autofs.service has begun starting up. Apr 21 12:02:20 server1 systemd[1]: Started Automounts filesystems on demand. -- Subject: Unit autofs.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit autofs.service has finished starting up. -- -- The start-up result is done. Finally I tried to prevent any umount by changing in /etc/sysconfig/autofs #OPTIONS="" to OPTIONS="-timeout=0" And I tried to add in /etc/auto.master at end of line --timeout=0 (/workdir /etc/auto.workdir --timeout=0) But besides this values there is an automatic restart every 30min Apr 21 13:34:41 server1 systemd: Stopping Automounts filesystems on demand... Apr 21 13:34:42 server1 systemd: Starting Automounts filesystems on demand... Apr 21 13:34:42 server1 systemd: Started Automounts filesystems on demand. Apr 21 14:04:42 server1 systemd: Stopping Automounts filesystems on demand... Apr 21 14:04:42 server1 systemd: Stopped Automounts filesystems on demand. Apr 21 14:04:42 server1 systemd: Starting Automounts filesystems on demand... Apr 21 14:04:42 server1 systemd: Started Automounts filesystems on demand. Apr 21 14:34:42 server1 systemd: Stopping Automounts filesystems on demand... Apr 21 14:34:42 server1 automount[11019]: umount_autofs_indirect: ask umount returned busy /vsaabrmount Apr 21 14:34:44 server1 systemd: Stopped Automounts filesystems on demand. Apr 21 14:34:44 server1 systemd: Starting Automounts filesystems on demand... Apr 21 14:34:44 server1 systemd: Started Automounts filesystems on demand. Switching back to RH 6 doesn't show this problem. Any suggestions? Thanks in advance Best regards Thomas NOVENTI Health SE | Tomannweg 6 | 81673 München Telefon +49 89 43184-153 | thomas.wiesc...@noventi.de | www.noventi.de Vorstand: Dr. Hermann Sommer (Vorsitzender) | Dr. Sven Jansen | Victor J. Castro Erweiterter Vorstand: Sven Bertram (CTO) | Dr. Verena Heeschen (CHRO) | Dr. Silvio Kusche (CMO) | Dr. Sven Simons (CCIO) | Björn Zeien (CSO) Aufsichtsratsvorsitzender: Uwe Geiß Sitz der Gesellschaft: München, Registergericht München HRB 234740 | USt-IdNr.: DE314305075 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [systemd-level]: how to set property to read only in systemd?
On Di, 21.04.20 19:54, www (ouyangxua...@163.com) wrote: > hi Lennart, > > > I mean the DBUS property. > > root@demoboard:/# busctl set-property org.freedesktop.DBus > /org/freedesktop/DBus org.freedesktop.DBus Features as 1 x > > Cannot set read-only property -- the default > > > > > root@demoboard:/# busctl set-property com.sugon.sensors.DISCRETE > /com/sugon/sensors/HDD/HDD4_Status xyz.openbmc_project.Sensor.DiscreteAll > FanDeviceInserted b true -- new add > > root@demoboard:/# > > > > I want the property on Dbus is read only. Just can modify by the > special method and cannot modify the property directly. How can I > change it like this? Is "com.sugon.sensors.DISCRETE" a service you implemented yourself? With the sd-bus API? In sd-bus you define a writable property in a vtable with the SD_BUS_WRITABLE_PROPERTY() macro, and a read-only one with SD_BUS_PROPERTY(). But not sure I grok your question properly. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [systemd-level]: how to set property to read only in systemd?
hi Lennart, I mean the DBUS property. root@demoboard:/# busctl set-property org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus Features as 1 x Cannot set read-only property -- the default root@demoboard:/# busctl set-property com.sugon.sensors.DISCRETE /com/sugon/sensors/HDD/HDD4_Status xyz.openbmc_project.Sensor.DiscreteAll FanDeviceInserted b true -- new add root@demoboard:/# I want the property on Dbus is read only. Just can modify by the special method and cannot modify the property directly. How can I change it like this? thanks, Byron At 2020-04-21 00:43:00, "Lennart Poettering" wrote: >On Mo, 20.04.20 23:00, www (ouyangxua...@163.com) wrote: > >> dear all; >> >> >> How to set some properties in systemd to read-only？ Who can give the sample >> code? > >I don't understand the question. Do you mean a D-Bus property? They >generally are read-only for unprivileged bus clients. With a PolicyKit >action configuration you can open them up, but typically unprivileged >clients can't change them. > >Lennart > >-- >Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Antw: [EXT] ^] 3 times which key is it
>>> "Ulrich Windl" schrieb am 21.04.2020 um 10:31 in Nachricht <5e9eaf7102a100038...@gwsmtp.uni-regensburg.de>: Damian Ivanov schrieb am 20.04.2020 um 17:30 in > Nachricht > <20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9 > tre > p_byb...@mail.gmail.com>: >> Hello! >> >> Please enlighten me: which key is ^] > > Isn't it Escape (ESC)? Sorry, I was wrong; that would be ^[ (27), but ^] is 29. > >> >> Br, >> Damian >> ___ >> systemd‑devel mailing list >> systemd‑de...@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd‑devel > > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [EXT] ^] 3 times which key is it
Seems not, ctr + ] worked. And when using nano all the ctrl keys are also marked as ^key On Tue, Apr 21, 2020 at 11:31 AM Ulrich Windl wrote: > > >>> Damian Ivanov schrieb am 20.04.2020 um 17:30 in > Nachricht > <20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9tre > p_byb...@mail.gmail.com>: > > Hello! > > > > Please enlighten me: which key is ^] > > Isn't it Escape (ESC)? > > > > > Br, > > Damian > > ___ > > systemd‑devel mailing list > > systemd‑de...@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/systemd‑devel > > > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: [EXT] ^] 3 times which key is it
>>> Damian Ivanov schrieb am 20.04.2020 um 17:30 in Nachricht <20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9tre p_byb...@mail.gmail.com>: > Hello! > > Please enlighten me: which key is ^] Isn't it Escape (ESC)? > > Br, > Damian > ___ > systemd‑devel mailing list > systemd‑de...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd‑devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] nspawn and mariadb /run/mysql
Hi, After bootstrapping os and mariadb into $DIR I booted the machine with: systemd-nspawn -D $DIR -b --resolv-conf=bind-host --capability=all I had to remove $DIR/etc/resolv.conf first as bind-host seems to fail if $DIR/etc/resolv.conf already exists. mariadb.service was failing, after looking into mysql.log I found that /run/mysql/mysql.sock (No such file or directory) /run is a temporary dir inside nspawn and not the actual $DIR/run So I went ahead and created /run/mysql (which of course is gone when the container is stopped) For mariadb to work it is also required to chown -R mysql:mysql /run/mysql which results in chown complaing no such group mysql The group is in /etc/groups and another attempt to add groupadd mysql would faill saying that the group exists. Using chmod -R 777 /run/mysql worked. Is there some permanent solution to have mariadb work, without recreating /run/mysql at container boot and even better with groups working? I tried various combinations of --private-users=pick --private-users-chown They result in machinectl --machine $DIR shell to fail (org.freedesktop.machine1 not provided by anything) and the root password never being accepted if on the container bootscreen. #systemctl --version systemd 245 (+suse.83.gc5aa158173 Ideas appreciated. Br, Damian ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [RFC PATCH] udev: rename the persistent link for ATA devices
ATA devices should use the ATA ids like port number and (possibly)
master/slave or multiplier id, not the generic SCSI ID.
Currently only port number is included in the link. With this patch
the link would be able to support more cases, which are a) when the
device is behind a port multiplexer b) the distinction between master
and slave (distinguished by target id).
It also creates a compatible link for the old format in rules file
60-persistent-storage.rules.
Signed-off-by: Lidong Zhong
---
rules.d/60-persistent-storage.rules | 3 +++
src/udev/udev-builtin-path_id.c | 15 +--
2 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/rules.d/60-persistent-storage.rules
b/rules.d/60-persistent-storage.rules
index 01586690bd..633b3dbfbe 100644
--- a/rules.d/60-persistent-storage.rules
+++ b/rules.d/60-persistent-storage.rules
@@ -93,6 +93,9 @@ ENV{DEVTYPE}=="disk", DEVPATH!="*/virtual/*",
IMPORT{builtin}="path_id"
KERNEL=="mmcblk[0-9]boot[0-9]", ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*",
SYMLINK+="disk/by-path/$env{ID_PATH}-boot%n"
KERNEL!="mmcblk[0-9]boot[0-9]", ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*",
SYMLINK+="disk/by-path/$env{ID_PATH}"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*",
SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"
+# ATA device compatible links
+KERNEL!="mmcblk[0-9]boot[0-9]", ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*ata*",
PROGRAM="/bin/sh -c 'echo $env{ID_PATH} | /bin/sed
s/\(^.*ata-[0-9]*\)/\1/g'",ENV{ID_PATH_ATA_COMPAT}="%c",
SYMLINK+="disk/by-path/$env{ID_PATH_ATA_COMPAT}"
+ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*ata*", PROGRAM="/bin/sh -c 'echo
$env{ID_PATH} | /bin/sed s/\(^.*ata-[0-9]*\)/\1/g'",
ENV{ID_PATH_ATA_COMPAT}="%c",
SYMLINK+="disk/by-path/${$env{ID_PATH_ATA_COMPAT}-part%n"
# legacy virtio-pci by-path links (deprecated)
KERNEL=="vd*[!0-9]", ENV{ID_PATH}=="pci-*",
SYMLINK+="disk/by-path/virtio-$env{ID_PATH}"
diff --git a/src/udev/udev-builtin-path_id.c b/src/udev/udev-builtin-path_id.c
index ca38f56087..fb12539781 100644
--- a/src/udev/udev-builtin-path_id.c
+++ b/src/udev/udev-builtin-path_id.c
@@ -256,11 +256,16 @@ static sd_device *handle_scsi_iscsi(sd_device *parent,
char **path) {
static sd_device *handle_scsi_ata(sd_device *parent, char **path) {
sd_device *targetdev, *target_parent;
_cleanup_(sd_device_unrefp) sd_device *atadev = NULL;
-const char *port_no, *sysname;
+const char *port_no, *sysname, *name;
+int host, bus, target, lun;
assert(parent);
assert(path);
+name = udev_device_get_sysname(parent);
+if (sscanf(name, "%d:%d:%d:%d", , , , ) != 4)
+return NULL;
+
if (sd_device_get_parent_with_subsystem_devtype(parent, "scsi",
"scsi_host", ) < 0)
return NULL;
@@ -275,7 +280,13 @@ static sd_device *handle_scsi_ata(sd_device *parent, char
**path) {
if (sd_device_get_sysattr_value(atadev, "port_no", _no) < 0)
return NULL;
-path_prepend(path, "ata-%s", port_no);
+if (bus != 0)
+/* Devices behind port multiplier have a bus != 0*/
+path_prepend(path, "ata-%s.%u.0", port_no, bus);
+else
+/* Master/slave are distinguished by target id */
+path_prepend(path, "ata-%s.%u", port_no, target);
+
return parent;
}
--
2.16.4
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
