[systemd-devel] RT wiki page outdated

http://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/ seems way outdated - none of parameters mentioned there exist anymore. What is the correct way to do the same on modern systemd? Thank you! ___ systemd-devel mailing list systemd-d

[systemd-devel] Use python-systemd with virtualenv or pyvenv

Hi, I'm trying to use python-systemd with a pyvenv: We use pyvenv to add different set of librairies on the server for each daemon without to disturb Python at the system level. I don't find a way to compile systemd with a pyvenv enabled. To by-pass the issue and ideally to be installable via PyP

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

2015-05-02 17:22 GMT+02:00 Jörg Thalheim : > On Sat, 2 May 2015 16:31:44 +0200 > Ludovic Gasc wrote: > > > 2015-05-02 16:18 GMT+02:00 Zbigniew Jędrzejewski-Szmek > > : > > > > > On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > > > > Ok, my bad, I didn't see JournalHandler class to

Re: [systemd-devel] [PATCH 3/3] Use a stamp file to avoid running systemd-fsck-root.service twice

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing

Re: [systemd-devel] [PATCH 3/3] Use a stamp file to avoid running systemd-fsck-root.service twice

On Sat, May 02, 2015 at 08:26:25PM +0300, Andrei Borzenkov wrote: > В Sat, 2 May 2015 13:16:59 -0400 > Zbigniew Jędrzejewski-Szmek пишет: > > > In the initramfs, we run systemd-fsck@.service. > > In the real system we run systemd-fsck-root.service. It is hard > > to pass the information that the

Re: [systemd-devel] [PATCH 3/3] Use a stamp file to avoid running systemd-fsck-root.service twice

В Sat, 2 May 2015 13:16:59 -0400 Zbigniew Jędrzejewski-Szmek пишет: > In the initramfs, we run systemd-fsck@.service. > In the real system we run systemd-fsck-root.service. It is hard > to pass the information that the latter should not run if the first > succeeded using unit state only. > > -

[systemd-devel] [PATCH 3/3] Use a stamp file to avoid running systemd-fsck-root.service twice

In the initramfs, we run systemd-fsck@.service. In the real system we run systemd-fsck-root.service. It is hard to pass the information that the latter should not run if the first succeeded using unit state only. - in the real system, we need a synchronization point between the fsck for root and

[systemd-devel] [PATCH 0/3] avoid running fsck twice

This is an attempt to fix the issue with fsck running twice. Patch 3/3 is the only important one, the other two are nice-to-have. dracut configuration also has to be modified to include /bin/touch. I'll work on a patch for that later. I also tried the approach listed in TODO: generate systemd-fsk

[systemd-devel] [PATCH 2/3] Allow $SYSTEMD_PRETEND_INITRD to override initramfs detection

When testing generators and other utilities, it is extremely useful to be able to trigger initramfs behaviour. We already allow $SYSTEMD_UNIT_PATH to modify systemd behaviour, this follows the same principle. --- src/shared/util.c | 18 -- 1 file changed, 12 insertions(+), 6 delet

[systemd-devel] [PATCH 1/3] generators: rename add_{root, usr}_mount to add_{sysroot, sysroot_usr}_mount

This makes it obvious that those functions are only usable in the initramfs. Also, add a warning when noauto, nofail, or automount is used for the root fs, instead of silently ignoring. Using those options would be a sign of significant misconfiguration, and if we bother to check for them, than le

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

On Sat, May 02, 2015 at 05:22:49PM +0200, Jörg Thalheim wrote: > On Sat, 2 May 2015 16:31:44 +0200 > Ludovic Gasc wrote: > > > 2015-05-02 16:18 GMT+02:00 Zbigniew Jędrzejewski-Szmek > > : > > > > > On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > > > > Ok, my bad, I didn't see Jou

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

On Sat, 2 May 2015 16:31:44 +0200 Ludovic Gasc wrote: > 2015-05-02 16:18 GMT+02:00 Zbigniew Jędrzejewski-Szmek > : > > > On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > > > Ok, my bad, I didn't see JournalHandler class to use with Python > > > logging: > > > > > http://www.freede

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

On Sat, May 02, 2015 at 04:31:44PM +0200, Ludovic Gasc wrote: > 2015-05-02 16:18 GMT+02:00 Zbigniew Jędrzejewski-Szmek : > > > On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > > > Ok, my bad, I didn't see JournalHandler class to use with Python logging: > > > > > http://www.freedesk

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

2015-05-02 16:18 GMT+02:00 Zbigniew Jędrzejewski-Szmek : > On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > > Ok, my bad, I didn't see JournalHandler class to use with Python logging: > > > http://www.freedesktop.org/software/systemd/python-systemd/journal.html#journalhandler-class

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

On Sat, May 02, 2015 at 03:34:52PM +0200, Ludovic Gasc wrote: > Ok, my bad, I didn't see JournalHandler class to use with Python logging: > http://www.freedesktop.org/software/systemd/python-systemd/journal.html#journalhandler-class > > Nevertheless, my question about communication between Python

Re: [systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

Ok, my bad, I didn't see JournalHandler class to use with Python logging: http://www.freedesktop.org/software/systemd/python-systemd/journal.html#journalhandler-class Nevertheless, my question about communication between Python and journald remains. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/

[systemd-devel] Journald logging handler for Python 3 and AsyncIO integration

Hi, With the new release of Debian Jessie and systemd+journald integration, I'm looking for how to modernize our Python 3 toolbox to build daemons. For now on Debian Wheezy, we use a SysLogHandler with UNIX socket: https://docs.python.org/3.4/library/logging.handlers.html#sysloghandler + a custom

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

> On May 2, 2015, at 3:48 AM, Lennart Poettering wrote: > >> On Fri, 01.05.15 08:29, Stephen Gallagher (sgall...@redhat.com) wrote: >> >> Right, so based on this information, it seems to me that in SSSD we >> need to be treating the 'systemd-user' PAM service the same way we do >> the 'cron' s

Re: [systemd-devel] [PATCH 2/2] udev: Allow detection of udevadm settle timeout

On Tue, Apr 21, 2015 at 12:41 AM, Tom Gundersen wrote: > On Mon, Apr 13, 2015 at 3:04 PM, Nir Soffer wrote: >> On Sat, Apr 11, 2015 at 6:58 PM, David Herrmann >> wrote: A program running this tool can detect a timeout (expected) or an error (unexpected), and can change the program flo

Re: [systemd-devel] networkd: Is auto-negotiation turned off when specifying parameters in a link file?

Dear poma, Thank you for the reply with a test and sorry for my late reply. I was unfortunately unable to test this on the server, as there was no maintenance window yet. It’s still on my todo list though. Am Donnerstag, den 09.04.2015, 00:28 +0200 schrieb poma: > On 08.04.2015 23:05, Lennart Po

[systemd-devel] networkd must start before nspawn@container

My host/conatiner networking are both managed by systemd-netwrokd. I have a bridge Br0 on host and vb-MyContainer for the conatiner. Both have a fix local IP. I boot container at host boot this way: -- $ cat /etc/systemd/system/systemd-nspawn@.service

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Fri, 01.05.15 08:29, Stephen Gallagher (sgall...@redhat.com) wrote: > Right, so based on this information, it seems to me that in SSSD we > need to be treating the 'systemd-user' PAM service the same way we do > the 'cron' service. The idea being that this is meant to handle > actions performed