From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] 'nobody' user for testing
Date: Thu, 16 Oct 2025 14:32:14 +0200 [thread overview]
Message-ID: <aPDlzuox-54oxTtp@yuki.lan> (raw)
In-Reply-To: <20250929083156.GA199802@pevik>
Hi!
> Short term solution will be Jan's suggestion to write simple "sudo" binary or
> even just let testers to fix the setup (i.e. fix it for us in openQA).
I guess that having a small helper to execute commands as a selected
user would be reasonable. We already have tst_sleep because the sleep
commands in different shells behaves differently.
Adding tst_sudo that would take an user and command to execute does make
sense here I suppose. And I think that the question if we need a
separate user for LTP testing is orthogonal.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-16 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:27 [LTP] [RFC] 'nobody' user for testing Petr Vorel
2025-09-22 8:48 ` Jan Stancek via ltp
2025-09-26 12:25 ` Petr Vorel
2025-10-06 9:48 ` Petr Vorel
2025-09-26 13:24 ` Andrea Cervesato via ltp
2025-09-29 8:31 ` Petr Vorel
2025-10-16 12:32 ` Cyril Hrubis [this message]
2025-10-16 13:09 ` Petr Vorel
2025-10-16 13:35 ` Cyril Hrubis
2025-10-16 14:07 ` Petr Vorel
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=aPDlzuox-54oxTtp@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox