All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: prctl patch for fpu faults
Date: Wed, 10 Oct 2001 22:31:22 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805324@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805302@msgid-missing>

I was thinking of hacking up the 'prctl' tool to take a PID as an
argument, that way it could set the flags for any task.  It would allow
an initscript to set init's flags, among other things.  Would such a
change qualify as a cleaner solution?

Jesse

On Wed, 10 Oct 2001, David Mosberger wrote:

> >>>>> On Wed, 10 Oct 2001 08:59:36 -0500 (CDT), Jack Steiner <steiner@sgi.com> said:
> 
>   Jack> There should be a way a site can change the default logging
>   Jack> behavior & have it apply to ALL tasks..
> 
> I agree.  In theory, if you can change the behavior of "init", you'll
> change the behavior of all subsequent tasks (the settings are
> inherited across fork).  If you're willing to hack /etc/inittab, you
> could probably do that with the "prctl" utility today (or perhaps even
> with prctl + a suitable kernel command line), but none of these
> solutions seem to be very pretty.  Perhaps someone can come up with a
> cleaner solution?
> 
> 	--david
> 




  parent reply	other threads:[~2001-10-10 22:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 23:42 [Linux-ia64] Re: prctl patch for fpu faults David Mosberger
2001-10-08 23:46 ` Jesse Barnes
2001-10-08 23:54 ` David Mosberger
2001-10-08 23:55 ` Jesse Barnes
2001-10-08 23:57 ` Jesse Barnes
2001-10-09  0:11 ` Jesse Barnes
2001-10-09 21:40 ` Jesse Barnes
2001-10-10 13:59 ` Jack Steiner
2001-10-10 14:18 ` n0ano
2001-10-10 16:34 ` Jesse Barnes
2001-10-10 20:18 ` Mallick, Asit K
2001-10-10 20:26 ` David Mosberger
2001-10-10 20:42 ` Keith Fish
2001-10-10 22:27 ` David Mosberger
2001-10-10 22:31 ` Jesse Barnes [this message]
2001-10-10 22:51 ` David Mosberger
2001-10-10 22:53 ` Khalid Aziz
2001-10-10 22:57 ` Jesse Barnes
2001-10-10 23:05 ` David Mosberger
2001-10-11  3:11 ` Mallick, Asit K
2001-10-11  3:21 ` David Mosberger

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=marc-linux-ia64-105590698805324@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.