[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAObL_7GqnS_2AA_yCtozVT6eiT9yM+LViutw3A+DFd+0z4=A5Q@mail.gmail.com>
Date: Thu, 5 Jun 2014 12:26:51 -0700
From: Andrew Lutomirski <luto@....edu>
To: Lennart Poettering <mzxreary@...inter.de>
Cc: "Luis R. Rodriguez" <mcgrof@...e.com>,
Ian Campbell <Ian.Campbell@...rix.com>,
Keir Fraser <keir@....org>, Tim Deegan <tim@....org>,
Ian Jackson <ian.jackson@...citrix.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
systemd-devel@...ts.freedesktop.org,
linux-security-module@...r.kernel.org,
Eric Biederman <ebiederm@...ssion.com>,
Jan Beulich <jbeulich@...e.com>,
xen-devel@...ts.xenproject.org,
"Andrew G. Morgan" <morgan@...nel.org>
Subject: Re: [systemd-devel] [PATCH v5 12/14] autoconf: xen: enable explicit
preference option for xenstored preference
On Thu, Jun 5, 2014 at 12:24 PM, Lennart Poettering
<mzxreary@...inter.de> wrote:
> On Thu, 05.06.14 20:01, Luis R. Rodriguez (mcgrof@...e.com) wrote:
>
>> > Hmm? You should "exec" the real daemon binary at the end, not just fork
>> > it off. That wait the shell script process is replaced by the daemon
>> > binary, which is what you want.
>>
>> I tried both just running it and also running exec foo; both presented
>> the same issue given that shell exec does not really execve.
>
> Hmmm? You shell's "exec" command doesn't actually execve()? What are you
> using? This doesn't sound very accurate...
$ strace -e execve /bin/sh -c 'exec /bin/echo test'
execve("/bin/sh", ["/bin/sh", "-c", "exec /bin/echo test"], [/* 54 vars */]) = 0
execve("/bin/echo", ["/bin/echo", "test"], [/* 54 vars */]) = 0
test
+++ exited with 0 +++
I get similar results on Ubuntu using dash.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists