All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Filz <m.filz@gmx.net>
To: cpufreq@www.linux.org.uk
Subject: Re: CHOWN PB
Date: Fri, 19 Sep 2003 08:47:01 +0200	[thread overview]
Message-ID: <03091908435100.00212@gate> (raw)
In-Reply-To: <3F6A35D7.8070605@wanadoo.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 19 September 2003 00:46, you wrote:
> Hi,
> Ok here is the deal :
> I would like to allow users from a given group (let say the cpufreq
> group) to have write acces to /proc/cpufreq and
> /proc/sys/cpu/0/speed...I try the following :
>
> $ chown root:cpufreq /proc/cpufreq
> $ chmod 664 /proc/cpufreq
> And then...
> $ ls -l /proc/cpufreq
> ...show me that nothing changes.
>
> Any idea on how to solve this problem ? Because login as root every time
> I want to change the frequency is quite boring ( I would like to be able
> to use button of my window manager to change it), and because of that
> other people that use my laptop can change the frequency because they
> don't have the root passwd...
> Thx in advance...
> Mike

This is one of the few cases where suid root is really useful. Put everything 
you want in a script, suid it and put it in the bin directory of your choice. 
If you set the ownership of the script to root.cpufreq you might even be able 
to restrict its use to the group; if not you would have the script to check 
for allowed users or something.
- -- 
GPG 1.2.1 signed
Fingerprint: 60B4 D8E3 9617 900C 6726  168F D677 5AAD D40F CCE7
Certserver : ldap://certserver.pgp.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/aqZl1ndardQPzOcRAsJoAJ0V5ZVh+sq5oUQJz2KIBCA7pFfPrwCg9vjg
CKlc8BOLk1gaOszRyITjv14=
=w4YI
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-09-19  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 22:46 CHOWN PB Toula Michael
2003-09-19  6:47 ` Michael Filz [this message]
2003-09-19  7:06   ` Norbert Preining
2003-09-28 11:53 ` Dominik Brodowski

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=03091908435100.00212@gate \
    --to=m.filz@gmx.net \
    --cc=cpufreq@www.linux.org.uk \
    /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.