What now?
08 Jun 2019 21:41 #136308
by Roguish
Attachments:
Please Log in or Create an account to join the conversation.
08 Jun 2019 21:50 #136309
by Grotius
It can be that you need to do : "sudo make setuid" in the src directory.
Insmod mean's your latency program can not load into the kernel.
But you are root now. And terminal output is complaining about your root session now.
Try to go back to user and then do your sudo latancy-histogram --verbose
command.
Insmod mean's your latency program can not load into the kernel.
But you are root now. And terminal output is complaining about your root session now.
Try to go back to user and then do your sudo latancy-histogram --verbose
command.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 17810
- Thank you received: 5925
08 Jun 2019 23:54 #136319
by tommylight
Replied by tommylight on topic What now?
Exactly what JT asked.
95% of the time it is not required to use "sudo", and using it causes some nice issues later on.
95% of the time it is not required to use "sudo", and using it causes some nice issues later on.
Please Log in or Create an account to join the conversation.
Time to create page: 0.213 seconds