From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top
Subject: Re: [PATCH 1/2] test/perf: Check for /sbin/sysctl with which(1), not simply sysctl
Date: Sat, 17 Sep 2022 19:51:45 +1000 [thread overview]
Message-ID: <YyWYsWmSl13XQSs5@yekko> (raw)
In-Reply-To: <20220917104436.28fe332e@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On Sat, Sep 17, 2022 at 10:44:36AM +0200, Stefano Brivio wrote:
> On Sat, 17 Sep 2022 13:27:32 +1000
> David Gibson <david(a)gibson.dropbear.id.au> wrote:
>
> > On Sat, Sep 17, 2022 at 01:55:33AM +0200, Stefano Brivio wrote:
> > > Otherwise, we're depending on having /sbin in $PATH. For some reason
> >
> > Huh. I wonder why this is working for me.
>
> Different shells, or different shell profiles, I guess?
>
> > > I didn't completely grasp, with the new command dispatch mechanism
> > > that's not the case anymore, even if I have /sbin in $PATH in the
> > > parent shell.
> >
> > For the guest, there's no mystery - there's no strong connection
> > between the shell environments there. We probably can control PATH
> > with our mbuto setup though.
> >
> > For the ns that is strange, though.
>
> I think the reason is that with:
>
> echo "nsenter $@ sh -c" > "${__enter}"
>
> you get a different behaviour than nsenter with an interactive shell
> (previous implementation). For example, on Debian, commands (by default)
> will run with dash instead of bash.
>
> In any case, just using 'which sysctl' looks wrong to me, and that can
> break for many other reasons, so I don't feel very inclined in digging
> into the actual reason and differences between environments here.
Yeah, fair enough.
Reviewed-by: David Gibson <david(a)gibson.dropbear.id.au>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-17 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 23:55 [PATCH 0/2] test: Fix two issues made apparent by new command dispatch Stefano Brivio
2022-09-16 23:55 ` [PATCH 1/2] test/perf: Check for /sbin/sysctl with which(1), not simply sysctl Stefano Brivio
2022-09-17 3:27 ` David Gibson
2022-09-17 8:44 ` Stefano Brivio
2022-09-17 9:51 ` David Gibson [this message]
2022-09-16 23:55 ` [PATCH 2/2] test/passt_in_ns: Consistent sleep commands before starting socat client Stefano Brivio
2022-09-17 3:32 ` David Gibson
2022-09-17 8:44 ` Stefano Brivio
2022-09-17 10:19 ` David Gibson
2022-09-17 11:28 ` Stefano Brivio
2022-09-19 1:48 ` David Gibson
2022-09-19 6:41 ` Stefano Brivio
2022-09-19 7:00 ` David Gibson
2022-09-19 8:24 ` Stefano Brivio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YyWYsWmSl13XQSs5@yekko \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).