-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Processes widget fails with ps from BusyBox #20
Comments
Busbox support sounds good to me. It would probably require us to do some check on the environment on start and adjust the So can you test this command: |
Unfortunately it is the complete manpage :(
With yours commands i get :
I removed pcpu and pmem (because it's not recognized) and i get things like this :
I don't see any problems with cropping (i have some very long "Command" entries). |
So it looks like |
The only way i find to get cpu or memory reporting is to use top. |
Some new ideas about different ways to fix this:
3 sounds best to me. We were originally using gopsutil to gather process information but I forget why we switched of it. And it should be easy to test gopsutil's implementation (I've just been busy). |
Note to self:
|
(Emphasis mine). Well, I found out why. CPU use quadruples under the I've filed shirou/gopsutil#842, and will leave this ticket open until a clear path forward is defined. @Mikiya83 FYI |
On a suggestion over in shirou/gopsutil#842 by @AtakanColak, I tried go-sysinfo. Despite eliminating the forking & parsing of output, and string manipulation and parsing to produce numbers, it's still twice as slow as forking |
Gory details are in shirou/gopsutil#842, but the summary is: a benchmark shows that elastic/go-sysinfo is marginally faster than the current forking/parsing code. It doesn't explain why |
Another hiccup: |
Required information:
gotop -v
): 2.0.1uname -a
: Linux 4.2.8 Add ability to send different signals to processes #1 SMP Fri Dec 28 00:59:23 CST 2018 x86_64 GNU/LinuxLogs :
"11:19:36 proc_linux.go:14: failed to retrieve processes: failed to execute 'ps' command: exit status 1"
On QNAP devices, ps command used Busybox version :
This version does not have "-axo" options so it fails. By default it shows processes of all users. Is it possible to have a version for BusyBox users ?
Thanks !
Original cjbassi#110
Submitter @Mikiya83
The text was updated successfully, but these errors were encountered: