This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/10724] stap should not retry if there is a permissions error
- From: "chwang at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 2 Oct 2009 18:05:23 -0000
- Subject: [Bug runtime/10724] stap should not retry if there is a permissions error
- References: <20091002180346.10724.chwang@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From chwang at redhat dot com 2009-10-02 18:05 -------
(In reply to comment #0)
> Currently, stap command attempts to delete modules and retry when it encounters
> an error. This should not happen when the error encountered is caused by a lack
> of permission [since relaunching won't change the permissions].
Reproduction notes:
1. Log in as a user without stapdev privileges
2. Attempt to run stap -e 'probe begin {printf("Hello World!")}'
3. Output will look like:
ERROR: You are trying to run stap as a normal user.
You should either be root, or be part of either group "stapdev" or group "stapusr".
Alternatively, your module must be compiled using the --unprivileged option and
signed by a trusted signer.
For more information, please consult the "SAFETY AND SECURITY" section of the
"stap(1)" manpage
Retrying, after attempted removal of module <blah> (rc -1)
ERROR: You are trying to run stap as a normal user.
You should either be root, or be part of either group "stapdev" or group "stapusr".
Alternatively, your module must be compiled using the --unprivileged option and
signed by a trusted signer.
For more information, please consult the "SAFETY AND SECURITY" section of the
"stap(1)" manpage
Note the repetition of the error message caused by an attempted relaunch.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10724
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.