[systemd-devel] getaddrinfo() API with systemd

2015-04-24 Thread Nanda Kumar
Hi, I am facing problem while querying DNS using getaddrinfo() API under a process initiated by systemd. Despite having nameserver entry in /etc/resolv.conf, the query fails to resolve. After few system call traces, it is found that the problem is due to systemd resolution. It seems like, for a pr

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Ivan Shapovalov
On 2015-04-25 at 04:00 +0300, Ivan Shapovalov wrote: > On 2015-04-24 at 16:04 +0200, Lennart Poettering wrote: > > [...] > > > > Actually, it really is about the UNIT_TRIGGERS dependencies only, > > since we don't do the retroactive deps stuff at all when we are > > coldplugging, it's conditionali

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Ivan Shapovalov
On 2015-04-24 at 16:04 +0200, Lennart Poettering wrote: > On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net) > wrote: > > > before we coldplug a unit, we should coldplug all units it might > > trigger, which are those with a listed UNIT_TRIGGERS dependency, as > > well as all tho

Re: [systemd-devel] systemd-nspawn trouble

2015-04-24 Thread Tobias Hunger
By the way: Is there a way to get the journal from a --ephemeral container? I had expected --link-journal=host to work, but --link-journal seems to not be allowed in any way. On Sat, Apr 25, 2015 at 12:14 AM, Tobias Hunger wrote: > Hello, > > sorry (again) for the delay. I unfortunately can not

Re: [systemd-devel] systemd-nspawn trouble

2015-04-24 Thread Tobias Hunger
Hello, sorry (again) for the delay. I unfortunately can not check into this as often as I would like:-( Lennart: Thank you for that patch, that does indeed fix my issue with read-only machine images. The networking issue does work better when iptables are used. All I needed to do was to make sur

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Alban Crequy
On Fri, Apr 24, 2015 at 5:34 PM, Lennart Poettering wrote: > On Fri, 24.04.15 17:10, Alban Crequy (al...@endocode.com) wrote: > >> On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering >> wrote: >> > On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: >> > >> >> Thanks for the commits

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Ivan Shapovalov
On 2015-04-24 at 20:19 +0200, Lennart Poettering wrote: > On Fri, 24.04.15 20:46, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > > On 2015-04-24 at 19:13 +0200, Lennart Poettering wrote: > > > On Fri, 24.04.15 20:06, Ivan Shapovalov (intelfx...@gmail.com) > > > wrote: > > > > > > > With this

Re: [systemd-devel] [PATCH] [RFC] umount: reduce verbosity

2015-04-24 Thread Jonathan Boulle
Naive question, perhaps, but why does systemd even need to umount when being run in a mount namespace? Can't we let the kernel tear them down when it exits? > > > > When rkt is started with --debug, the systemd logs are printed. When rkt > > is started without --debug, systemd is started with --lo

Re: [systemd-devel] KillUserProcesses timeout

2015-04-24 Thread Mikhail Morfikov
On Fri, 24 Apr 2015 19:04:53 +0200 Lennart Poettering wrote: > On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote: > > Sorry for the really late reply, still trying to work through piles of > mail. > > > > > Hmm, not sure I follow. > > > > > > > It only happens if I'm logge

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Andrei Borzenkov
В Fri, 24 Apr 2015 20:19:33 +0200 Lennart Poettering пишет: > On Fri, 24.04.15 20:46, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > > On 2015-04-24 at 19:13 +0200, Lennart Poettering wrote: > > > On Fri, 24.04.15 20:06, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > > > > > > With this p

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 20:46, Ivan Shapovalov (intelfx...@gmail.com) wrote: > On 2015-04-24 at 19:13 +0200, Lennart Poettering wrote: > > On Fri, 24.04.15 20:06, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > > > > With this patch applied, on `systemctl daemon-reload` I get the > > > following: > >

Re: [systemd-devel] [PATCH] [PATCH v2] PrivateDevices: fix /dev mount when a service is chrooted

2015-04-24 Thread Lennart Poettering
On Fri, 20.02.15 13:59, Alban Crequy (alban.cre...@gmail.com) wrote: Sorry for the late review, so much is still queued up! > From: Alban Crequy > > When a service is chrooted with the option RootDirectory=/opt/..., then > the option PrivateDevices=true must mount the private /dev in > $RootDir

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 20:06, Ivan Shapovalov (intelfx...@gmail.com) wrote: > With this patch applied, on `systemctl daemon-reload` I get the > following: Any chance you can do the same with debugging on? "systemd-analyze set-log-level debug" right before the daemon-reload? That should show the transa

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Ivan Shapovalov
On 2015-04-24 at 16:20 +0200, Lennart Poettering wrote: > On Fri, 24.04.15 16:04, Lennart Poettering (lenn...@poettering.net) > wrote: > > > On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net > > ) wrote: > > > > > before we coldplug a unit, we should coldplug all units it migh

Re: [systemd-devel] KillUserProcesses timeout

2015-04-24 Thread Lennart Poettering
On Tue, 27.01.15 04:28, Mikhail Morfikov (mmorfi...@gmail.com) wrote: Sorry for the really late reply, still trying to work through piles of mail. > > > Hmm, not sure I follow. > > > > It only happens if I'm logged in as root in tmux. > > > The session is shown as closing, that's good. Can y

Re: [systemd-devel] machinectl: Support for cache cleaning

2015-04-24 Thread Lennart Poettering
On Mon, 23.02.15 10:54, Peter Paule (systemd-de...@fedux.org) wrote: > Hi Lennart, > > I asked myself how I can get rid of those broken "temporary" subvolumes, to > re-pull the image: > > drwxr-xr-x 1 root root 158 Feb 20 18:46 > .dkr-00b2b6c6a2f93b2dde1d46b06cff32de82dabfd3b5ac6a8f27c5064f4

Re: [systemd-devel] [PATCH] units: add SecureBits

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 16:42, Topi Miettinen (toiwo...@gmail.com) wrote: > > I think all long-running ones that reasonably can already do. I mean, > > things like logind simple need too many caps, it's really not worth > > trying to make them run under a different uid, because they have so > > much priv

Re: [systemd-devel] Removing image from /var/lib/machines

2015-04-24 Thread Lennart Poettering
On Sun, 22.02.15 09:09, Peter Paule (systemd-de...@fedux.org) wrote: > Does it make sense to avoid copying /etc/resolv.conf to a container if > the filesystem is read-only? > > sudo /usr/bin/systemd-nspawn --read-only -M docker-centos-nginx > --read-only /usr/sbin/nginx > > Failed to cop

Re: [systemd-devel] Removing image from /var/lib/machines

2015-04-24 Thread Lennart Poettering
On Sun, 22.02.15 07:54, Peter Paule (systemd-de...@fedux.org) wrote: > Excerpts from Peter Paule's message of 2015-02-21 19:42:49 +0100: > > I tried 219 on a different machine as well. I got some "Permission > > denied errors" for importd as well. I "fixed" them by running importd > > from console

Re: [systemd-devel] Removing image from /var/lib/machines

2015-04-24 Thread Lennart Poettering
On Fri, 20.02.15 14:23, Peter Paule (systemd-de...@fedux.org) wrote: > > Zitat von Lennart Poettering : > > >On Thu, 19.02.15 19:46, Peter Paule (systemd-de...@fedux.org) wrote: > > > >>BTW: > >> > >>--dkr-index-url cannot handle http redirects > >> > >>By accident I tried "http://index.docker.i

Re: [systemd-devel] Updating existing docker image via machinectl

2015-04-24 Thread Lennart Poettering
On Fri, 20.02.15 14:11, Peter Paule (systemd-de...@fedux.org) wrote: heya! > Here's a small patch for changing the documentation. Sorry for the late review! I think this patch is a bit misleading, since "--force" actually drops the old instance, and that's hardly "updating", that's "replacing w

Re: [systemd-devel] [PATCH] units: add SecureBits

2015-04-24 Thread Topi Miettinen
On 04/24/15 14:52, Lennart Poettering wrote: > On Sat, 14.02.15 12:32, Topi Miettinen (toiwo...@gmail.com) wrote: > > Sorry for the late response, still going through piles of mail. > >> No setuid programs are expected to be executed, so add >> SecureBits=no-setuid-fixup no-setuid-fixup-l

Re: [systemd-devel] Cgroup limits for user processes

2015-04-24 Thread Lennart Poettering
On Wed, 18.02.15 12:48, Mikhail Morfikov (mmorfi...@gmail.com) wrote: Sorry for the late reply, still working on keeping up with the piles of mail that queued up. > What is the best way to set cgroup limits for user processes? I mean the > individual processes. I know that you can set limits for

[systemd-devel] [HEADSUP] Removal of shutdownd

2015-04-24 Thread Daniel Mack
The only purpose of the little helper daemon called shutdownd is to keep track and execute a scheduled shutdown. It prints utmp wall notifications to TTYs in periodic intervals, makes sure to create the /run/nologin and /run/systemd/shutdown/scheduled files, and eventually, once the timeout is reac

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 17:10, Alban Crequy (al...@endocode.com) wrote: > On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering > wrote: > > On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: > > > >> Thanks for the commits. They don't seem related to containers. > >> > >> I can reproduce m

Re: [systemd-devel] Fail to reset-failed as user

2015-04-24 Thread Lennart Poettering
On Sat, 14.02.15 19:37, Olivier Brunel (j...@jjacky.com) wrote: Heya! Sorry for responding so late again, but I think we can close this now: > #0 bus_message_enter_struct (m=0x7f5fb0cb88b0, c=0x7f5fb0cb8250, > contents=0x7f5faef0d152 "bba{ss}", item_size=0x7fffcebd48e8, > offsets=0x7fffcebd

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Alban Crequy
On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering wrote: > On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: > >> Thanks for the commits. They don't seem related to containers. >> >> I can reproduce my issue on git-master: >> >> sudo ~/git/systemd/systemd-nspawn --register=false

Re: [systemd-devel] [PATCH] units: add SecureBits

2015-04-24 Thread Lennart Poettering
On Sat, 14.02.15 12:32, Topi Miettinen (toiwo...@gmail.com) wrote: Sorry for the late response, still going through piles of mail. > No setuid programs are expected to be executed, so add > SecureBits=no-setuid-fixup no-setuid-fixup-locked > to unit files. > >>> > >>> So, hmm, afte

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 17:23, Ivan Shapovalov (intelfx...@gmail.com) wrote: > I think I agree with this idea. I just didn't know how to handle > potentially unbounded recursion. Maybe we can do something along these > lines (pseudocode): > > while (any units left to coldplug) > for (unit in hashmap

Re: [systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 17:33, Mantas Mikulėnas (graw...@gmail.com) wrote: > >> > Any idea what the precise syscall is that triggers that? i.e. what > >> > strace says? > >> > >> It kind of makes sense when stdout is a socket, since > >> open(/dev/stdout) or open(/proc/self/fd/*) doesn't just dup that fd

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-04-24 Thread Lennart Poettering
On Fri, 06.03.15 16:17, Michael Biebl (mbi...@gmail.com) wrote: > 2015-03-06 11:20 GMT+01:00 Didier Roche : > > It seems like tmp.mount unit was skipped as nothing declared any explicit > > dependency against it. What seems to confirm this is that if I add any > > enabled foo.service which declare

Re: [systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Mantas Mikulėnas
On Fri, Apr 24, 2015 at 4:53 PM, Lennart Poettering wrote: > On Fri, 24.04.15 16:51, Mantas Mikulėnas (graw...@gmail.com) wrote: > >> On Fri, Apr 24, 2015 at 4:24 PM, Lennart Poettering >> wrote: >> > On Fri, 24.04.15 12:06, Peter Paule (systemd-de...@fedux.org) wrote: >> > >> >> Hi, >> >> >> >>

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Ivan Shapovalov
not yet marked)On 2015-04-24 at 15:52 +0200, Lennart Poettering wrote: > On Wed, 25.02.15 21:40, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > Ivan, > > > Because the order of coldplugging is not defined, we can reference > > a > > not-yet-coldplugged unit and read its state while it has not

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 16:04, Lennart Poettering (lenn...@poettering.net) wrote: > On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net) wrote: > > > before we coldplug a unit, we should coldplug all units it might > > trigger, which are those with a listed UNIT_TRIGGERS dependency, as >

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net) wrote: > before we coldplug a unit, we should coldplug all units it might > trigger, which are those with a listed UNIT_TRIGGERS dependency, as > well as all those that retroactively_start_dependencies() and > retroactively_stop_d

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 15:52, Lennart Poettering (lenn...@poettering.net) wrote: > On Wed, 25.02.15 21:40, Ivan Shapovalov (intelfx...@gmail.com) wrote: > > Ivan, > > > Because the order of coldplugging is not defined, we can reference a > > not-yet-coldplugged unit and read its state while it has not

Re: [systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 16:51, Mantas Mikulėnas (graw...@gmail.com) wrote: > On Fri, Apr 24, 2015 at 4:24 PM, Lennart Poettering > wrote: > > On Fri, 24.04.15 12:06, Peter Paule (systemd-de...@fedux.org) wrote: > > > >> Hi, > >> > >> I run nginx in a CentOS 7.0 container via systemd-nspawn. nginx logs t

Re: [systemd-devel] [PATCHv2] core: do not spawn jobs or touch other units during coldplugging

2015-04-24 Thread Lennart Poettering
On Wed, 25.02.15 21:40, Ivan Shapovalov (intelfx...@gmail.com) wrote: Ivan, > Because the order of coldplugging is not defined, we can reference a > not-yet-coldplugged unit and read its state while it has not yet been > set to a meaningful value. > > This way, already active units may get start

Re: [systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Mantas Mikulėnas
On Fri, Apr 24, 2015 at 4:24 PM, Lennart Poettering wrote: > On Fri, 24.04.15 12:06, Peter Paule (systemd-de...@fedux.org) wrote: > >> Hi, >> >> I run nginx in a CentOS 7.0 container via systemd-nspawn. nginx logs to >> stderr/stdout via configuration to capture logs via journald. >> >> nginx.conf

Re: [systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 12:06, Peter Paule (systemd-de...@fedux.org) wrote: > Hi, > > I run nginx in a CentOS 7.0 container via systemd-nspawn. nginx logs to > stderr/stdout via configuration to capture logs via journald. > > nginx.conf > > error_log /dev/stderr warn; > > > If I use systemd 219-1

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 13:37, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > >> the exact name of the option and semantics to specify it to > >> initramfs-tools is different from dracut's (but that's typical) but > >> said equivalent feature does exist in the major other initramfs > >> implem

Re: [systemd-devel] [PATCH] core: don't change removed devices to state "tentative" [was: Re: [PATCH] unit: When stopping due to BindsTo=, log which unit caused it]

2015-04-24 Thread Martin Pitt
Hey Lennart, Lennart Poettering [2015-04-24 12:37 +0200]: > I only gave this light testing, I'd really appreciate if you could > test this, if this still does the right thing! Done (in QEMU), still works fine. I. e. it properly cleans up stale mounts. Thanks for cleaning this up, this looks nice!

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

2015-04-24 Thread Dimitri John Ledkov
On 24 April 2015 at 10:06, Lennart Poettering wrote: > On Thu, 23.04.15 21:04, Dimitri John Ledkov (dimitri.j.led...@intel.com) > wrote: > >> On 23 April 2015 at 13:08, Lennart Poettering wrote: >> > On Thu, 23.04.15 19:33, Andrei Borzenkov (arvidj...@gmail.com) wrote: >> > >> >> > > > What does

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Lennart Poettering
On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: > Thanks for the commits. They don't seem related to containers. > > I can reproduce my issue on git-master: > > sudo ~/git/systemd/systemd-nspawn --register=false --bind > $HOME/tmp/vol -D debian-tree -b > > Then, in the containe

Re: [systemd-devel] [PATCH] core: don't change removed devices to state "tentative" [was: Re: [PATCH] unit: When stopping due to BindsTo=, log which unit caused it]

2015-04-24 Thread Lennart Poettering
On Fri, 13.03.15 08:30, Martin Pitt (martin.p...@ubuntu.com) wrote: > From 05ffa415fa4f75f2e71830d47179b6f4a67c7215 Mon Sep 17 00:00:00 2001 > From: Martin Pitt > Date: Fri, 13 Mar 2015 08:23:02 +0100 > Subject: [PATCH] core: don't change removed devices to state "tentative" > > Commit 628c89c i

[systemd-devel] [systemd-nspawn] nginx: [emerg] open() "/dev/stderr" failed (6: No such device or address)

2015-04-24 Thread Peter Paule
Hi, I run nginx in a CentOS 7.0 container via systemd-nspawn. nginx logs to stderr/stdout via configuration to capture logs via journald. nginx.conf error_log /dev/stderr warn; If I use systemd 219-1 (-1 is the package number of Arch Linux) which seems to be a non-patched systemd 219,

Re: [systemd-devel] [PATCH v2] network: Implement fallback DHCPv6 prefix handling for older kernels

2015-04-24 Thread Patrik Flykt
Hi, On Fri, 2015-04-10 at 14:03 +0300, Patrik Flykt wrote: > Version 2 attempts to resolve IPv6 address assignment issues at run time, > first by adding IFA_FLAGS, then without. > > Please test with kernels < 3.14 and >= 3.14. This may be a case of too few people actually using DHCPv6

Re: [systemd-devel] Supporting ExecStartPre= and friends in `systemctl set-property` or `systemd-run -p`

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 04:07, Ivan Shapovalov (intelfx...@gmail.com) wrote: > - do `systemd-run` twice and somehow set up the dependencies between > two transient units I'd be happy to take a patch that allows configuring deps for transient units when constructing them. Lennart -- Lennart Poetteri

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 09:05, Jan Synacek (jsyna...@redhat.com) wrote: > Lennart Poettering writes: > > > On Fri, 20.02.15 10:56, Jan Synacek (jsyna...@redhat.com) wrote: > > > > Sorry for the late review. > > > > What's the precise background of this? Can you elaborate? Is there > > some feature requ

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

2015-04-24 Thread Lennart Poettering
On Thu, 23.04.15 21:04, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > On 23 April 2015 at 13:08, Lennart Poettering wrote: > > On Thu, 23.04.15 19:33, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > > >> > > > What does this actually do? Is the specified key file read from the > >>

Re: [systemd-devel] [PATCH] cryptsetup-generator: support rd.luks.key=keyfile:keyfile_device

2015-04-24 Thread Jan Synacek
Lennart Poettering writes: > On Fri, 20.02.15 10:56, Jan Synacek (jsyna...@redhat.com) wrote: > > Sorry for the late review. > > What's the precise background of this? Can you elaborate? Is there > some feature request for this? Hi, I can see that Andrei already answered most of your questions.