From: Clark Williams <williams@redhat.com>
To: Josh Cartwright <josh.cartwright@ni.com>
Cc: John Kacur <jkacur@redhat.com>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
linux-rt-users@vger.kernel.org
Subject: Re: Don't reference non-standard realtime group
Date: Thu, 18 Oct 2012 21:12:05 -0500 [thread overview]
Message-ID: <20121018211205.21f5f908@redhat.com> (raw)
In-Reply-To: <20121018161321.GE11335@beefymiracle.amer.corp.natinst.com>
[-- Attachment #1: Type: text/plain, Size: 1799 bytes --]
On Thu, 18 Oct 2012 11:13:21 -0500
Josh Cartwright <josh.cartwright@ni.com> wrote:
> On Tue, Oct 16, 2012 at 01:13:35AM +0200, John Kacur wrote:
> >
> >
> > On Sun, 2 Sep 2012, Uwe Kleine-König wrote:
> >
> > > On Wed, Jul 13, 2011 at 10:48:31PM +0200, Uwe Kleine-König wrote:
> > > > There is no dedicated realtime group in most distributions. So make the
> > > > error message a bit more understandable for people not running Redhat
> > > > MRG.
> >
> > I thought we rejected this (via irc) the first time you sent it. The idea
> > of a realtime group is pretty generic, but sure, it isn't there by default
> > if you don't create it. However, the worse thing about this patch is that
> > your message is in no way clearer than the original. It's longer though.
>
> How do you feel about this wording?
>
> Signed-off-by: Josh Cartwright <josh.cartwright@ni.com>
>
> diff --git a/src/lib/rt-utils.c b/src/lib/rt-utils.c
> index f4da4b3..e799c15 100644
> --- a/src/lib/rt-utils.c
> +++ b/src/lib/rt-utils.c
> @@ -264,8 +264,11 @@ int check_privs(void)
> /* try to change to SCHED_FIFO */
> param.sched_priority = 1;
> if (sched_setscheduler(0, SCHED_FIFO, ¶m)) {
> - fprintf(stderr, "Unable to change scheduling policy!\n");
> - fprintf(stderr, "either run as root or join realtime group\n");
> + fprintf(stderr, "Unable to change scheduling policy.\n");
> + fprintf(stderr, "This likely means you lack real-time privileges.\n");
> + fprintf(stderr, "It may be necessary to run as root or create/join a 'realtime' group.\n");
> + fprintf(stderr, "More details at the RTWiki:\n");
> + fprintf(stderr, "https://rt.wiki.kernel.org/index.php/Frequently_Asked_Questions\n");
> return 1;
> }
>
I'm good with this.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-10-19 2:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 20:48 Don't reference non-standard realtime group Uwe Kleine-König
2012-09-02 19:49 ` Uwe Kleine-König
2012-09-03 6:10 ` "g_serial: fix deadlock with PREEMPT_RT enabled" still not integrated Gregoire Gentil
2012-09-03 6:24 ` TI wl1271 wireless bug with 3.4-rt17 Gregoire Gentil
2012-09-04 14:11 ` Josh Cartwright
2012-09-05 1:22 ` Gregoire Gentil
2012-09-06 3:48 ` Josh Cartwright
2012-09-06 4:22 ` Gregoire Gentil
2012-09-09 22:42 ` Gregoire Gentil
2012-09-09 22:51 ` how to put in higher priority a thread in rt-kernel? Gregoire Gentil
2012-09-10 3:52 ` Mike Galbraith
2012-09-10 5:23 ` Gregoire Gentil
2012-09-10 16:20 ` Clark Williams
2012-10-15 23:13 ` Don't reference non-standard realtime group John Kacur
2012-10-16 18:26 ` Josh Cartwright
2012-10-18 16:13 ` Josh Cartwright
2012-10-19 2:12 ` Clark Williams [this message]
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=20121018211205.21f5f908@redhat.com \
--to=williams@redhat.com \
--cc=jkacur@redhat.com \
--cc=josh.cartwright@ni.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).