tags 862461 + patch
thanks
I agree with Nathaniel, the currently displayed message is too
confusing for regular users. A proper message should be displayed,
even if it means a (small!) deviation from upstream.
I am attaching a patch here, please consider!
Description: Report that root access is r
Dear Thomasz and Ben,
Many thanks for the explanation. I can confirm that the workaround is
effective. (In hindsight the man page has somewhat documented this
behavior under the ``--kernel'' flag.)
The only thing I have to add is that an edit to this part of the man
page may be in order:
On 14/05/17 20:58, Ben Hutchings wrote:
> On Sun, 2017-05-14 at 10:43 +0200, Tomasz Buchert wrote:
> > On 12/05/17 18:54, Nathaniel Beaver wrote:
> > > [...]
> >
> > Thank you, Nathaniel.
> >
> > I confirm the problem. A safe bet is that
> > https://lkml.org/lkml/2016/1/11/587 is the cause. You ca
On Sun, 2017-05-14 at 10:43 +0200, Tomasz Buchert wrote:
> On 12/05/17 18:54, Nathaniel Beaver wrote:
> > [...]
>
> Thank you, Nathaniel.
>
> I confirm the problem. A safe bet is that
> https://lkml.org/lkml/2016/1/11/587 is the cause. You can verify that
> /proc/sys/kernel/perf_event_paranoid c
On 12/05/17 18:54, Nathaniel Beaver wrote:
> [...]
Thank you, Nathaniel.
I confirm the problem. A safe bet is that
https://lkml.org/lkml/2016/1/11/587 is the cause. You can verify that
/proc/sys/kernel/perf_event_paranoid contains "3". By running
echo 2 | sudo tee /proc/sys/kernel/perf_even
Package: tiptop
Version: 2.2-2
Severity: important
Dear Maintainer,
Running tiptop results in a return status of 1 and this on stderr:
syscall: Operation not permitted
Could not perform syscall.
Don't know why...
It runs as expected as root or using sudo.
The homepage for tiptop lists "No r
6 matches
Mail list logo
