From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Karel Zak <kzak@redhat.com>
Cc: "util-linux@vger.kernel.org" <util-linux@vger.kernel.org>,
10317@debbugs.gnu.org
Subject: Re: su: -l and -p should not be used together
Date: Wed, 29 May 2013 11:55:10 +0200 [thread overview]
Message-ID: <51A5D07E.8000603@bernhard-voelker.de> (raw)
In-Reply-To: <20130529094010.GF30341@x2.net.home>
Hi Karel,
On 05/29/2013 11:40 AM, Karel Zak wrote:
> diff --git a/login-utils/su-common.c b/login-utils/su-common.c
> index ba2a616..a41d015 100644
> --- a/login-utils/su-common.c
> +++ b/login-utils/su-common.c
> @@ -810,6 +810,11 @@ su_main (int argc, char **argv, int mode)
> ++optind;
> }
>
> + if (simulate_login && !change_environment) {
> + warnx(_("ignore --preserve-environment, it's mutually exclusive to --login."));
> + change_environment = true;
> + }
> +
thanks.
As the change was in su-common.c, this also affects runuser.
I think this should then be documented in runuser.1, too, right?
Have a nice day,
Berny
next prev parent reply other threads:[~2013-05-29 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 10:57 su: -l and -p should not be used together Bernhard Voelker
2013-05-29 9:40 ` Karel Zak
2013-05-29 9:55 ` Bernhard Voelker [this message]
2013-06-07 9:28 ` Karel Zak
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=51A5D07E.8000603@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=10317@debbugs.gnu.org \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/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