From: Wiktor <victorjan@poczta.onet.pl>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFD] 'nice' attribute for executable files
Date: Fri, 01 Apr 2005 17:40:04 +0200 [thread overview]
Message-ID: <424D6B54.2090200@poczta.onet.pl> (raw)
In-Reply-To: <200503311556.j2VFu9Hc007903@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
>
> Even better: Write a C wrapper for each affected program that just renices
> it as needed.
I suggest to implement scalable solution, so the final user wont't have
to write separate wrapper for *each* program. universal wrapper is
better solution, but (now i know, that implementing something that can
be dangerous if used incorrectly is so evil, that only the devil could
have proposed it) it forces use of database (that normally would be kept
in filesystem's file metadata) and if some-malicious-person would have
accessed it in write mode (as result of wrong file permissions), the
system performerance would be in danger. in my solution, there is
per-file attribute, accessible only for root, and if hacker has root
permissions, existence of nice attribute is meaningless.
--
wixor
May the Source be with you.
next prev parent reply other threads:[~2005-04-01 15:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ed33rit.1e148rh@ifi.uio.no>
2005-03-29 20:45 ` [RFD] 'nice' attribute for executable files Bodo Eggert
2005-03-30 16:07 ` Wiktor
2005-03-30 16:55 ` Måns Rullgård
2005-03-30 17:27 ` Wiktor
2005-03-30 19:03 ` Måns Rullgård
2005-03-30 20:16 ` Wiktor
2005-03-30 20:43 ` Måns Rullgård
2005-04-01 15:26 ` Wiktor
2005-04-01 16:07 ` Måns Rullgård
2005-03-31 5:46 ` Jan Engelhardt
2005-03-31 15:56 ` Horst von Brand
2005-03-31 16:05 ` Måns Rullgård
2005-04-01 15:40 ` Wiktor [this message]
2005-04-01 16:12 ` Måns Rullgård
2005-04-01 17:27 ` Horst von Brand
2005-03-30 19:40 ` Bodo Eggert
2005-03-30 21:03 ` Lee Revell
2005-03-29 19:55 Wiktor
2005-03-29 21:02 ` Lee Revell
2005-03-30 19:55 ` Bill Davidsen
2005-03-31 5:51 ` Matt Mackall
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=424D6B54.2090200@poczta.onet.pl \
--to=victorjan@poczta.onet.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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