Multi-Core-System-Monitor icon indicating copy to clipboard operation
Multi-Core-System-Monitor copied to clipboard

No Disk IO information

Open pdelre opened this issue 9 years ago • 8 comments

I am running 1.5 on Linux Mint 17.2 as a VirtualBox guest on a Windows host. I am not getting any Disk activity that is being measured. I have sysstat installed and both iotop and htop can display disk usage when run under sudo.

Is there anything else that needs to be done so the applet has access to the disk activity? Does it need sudo access (sounds like a bad idea in general to try and enable for an applet).

Thank you!

pdelre avatar Nov 06 '15 13:11 pdelre

No the applet really should not need sudo permissions. (yeah that would be bad).

I am not sure what is happening. I use the libgtop gjs bindings for all the data gathered cpu, mem, etc.

When you open the preferences and go the the Disk tab; do you see the file system (mount point) you want to monitor?

On Fri, Nov 6, 2015 at 7:45 AM, Paul DelRe [email protected] wrote:

I am running 1.5 on Linux Mint 17.2 as a VirtualBox guest on a Windows host. I am not getting any Disk activity that is being measured. I have sysstat installed and both iotop and htop can display disk usage when run under sudo.

Is there anything else that needs to be done so the applet has access to the disk activity? Does it need sudo access (sounds like a bad idea in general to try and enable for an applet).

Thank you!

— Reply to this email directly or view it on GitHub https://github.com/ccadeptic23/Multi-Core-System-Monitor/issues/8.

ccadeptic23 avatar Nov 07 '15 22:11 ccadeptic23

Here's a shot of the preferences with the System Monitor in the background. It has slipped my mind, but I did select to use lvm during the installation provisioning.

image

pdelre avatar Nov 09 '15 20:11 pdelre

Just to eliminate the simple. Did u mean to set your width all the way down? That will make it "disappear". ie pixel width of 1 On Nov 9, 2015 2:57 PM, "Paul DelRe" [email protected] wrote:

Here's a shot of the preferences with the System Monitor in the background. It has slipped my mind, but I did select to use lvm during the installation provisioning.

[image: image] https://cloud.githubusercontent.com/assets/1379248/11046252/4d5cfe80-86fa-11e5-81d8-868fe5ba2a91.png

— Reply to this email directly or view it on GitHub https://github.com/ccadeptic23/Multi-Core-System-Monitor/issues/8#issuecomment-155190783 .

ccadeptic23 avatar Nov 09 '15 21:11 ccadeptic23

It's displays a width of 30, but seems that the tabs place the position of the slider button in different positions (Network and Disk, 30 is far left; CPU and Memory is about 25% of left).

Also to try and eliminate confusion, I've attached a screen of doing a find operation with sudo iotop in the background. I would expect the Disk applet to display something higher than 0/baseline.

image

pdelre avatar Nov 09 '15 21:11 pdelre

Oh expletive-deleted

I have noticed also that many operations do not seem to register on my system. I mostly attributed this to caching. Now that you mention it, and i am looking closer with you, I see iotop giving much different results that the applet on my system too. Yep this is a expletive-worthy problem.

I am beginning to worry that this could be a bug upstream. I am loath to introduce another dependency but the gtop bindings have several missing functions which should be there according to the c documentation. They clearly disabled them in the gir js binding and I never had time to determine why, so I worked around it.

The disk monitoring features of the libgtop library I am using were hard to use and many of them were disabled.

At one point I tried to find which developers were responsible for the bindings, but I didnt find them and got distracted by something else ;).

Anyway, I have encountered a similar dilemma before when working on this applet. So, Ill try to summarize my thoughts on the issue:

I am thinking that we probably should replace monitoring api, atleast for the disk io.

The problem is that I don't want users to need to either compile code, or to add a ppa. To me that is too much for an applet developer to ask. It should just work, or if a package is not installed it should be so standard that it will definitely be in the repo. That way I can have the user install it.

Additionally, calling command line tools via system calls will introduce way too much overhead. I shouldn't be forking a process every time I need data.

This means that we are restricted to libraries with gjs bindings (of which the last time i check 98% have zero documentation) or we could hopefully find and interact with a already present service, hoping that gnome or something in our software stack can feed us this data. Im thinking of something like DBUS or GDBUS. (I have no experience with dbus.)

What do you think? Have you done anything similar to this in the past?

On Mon, Nov 9, 2015 at 3:34 PM, Paul DelRe [email protected] wrote:

It's displays a width of 30, but seems that the tabs place the position of the slider button in different positions (Network and Disk, 30 is far left; CPU and Memory is about 25% of left).

Also to try and eliminate confusion, I've attached a screen of doing a find operation with sudo iotop in the background. I would expect the Disk applet to display something higher than 0/baseline.

[image: image] https://cloud.githubusercontent.com/assets/1379248/11047280/845decaa-86ff-11e5-8688-18c19270a8bd.png

— Reply to this email directly or view it on GitHub https://github.com/ccadeptic23/Multi-Core-System-Monitor/issues/8#issuecomment-155204190 .

ccadeptic23 avatar Nov 10 '15 02:11 ccadeptic23

I have not developed client side myself. It sounds like your decisions are practical given the applet ecosystem (no additional repos/compiling/forking/etc).

pdelre avatar Nov 10 '15 13:11 pdelre

Hello, @ccadeptic23 . First of all thanks for a nice applet. Do you have any news about this problem? Disk usage is not working for me as well (and I'm not using VM). Any ideas how to debug it? Thanks in advance

ckorobov avatar Mar 15 '16 10:03 ckorobov

I'm having the same problem. Clean install of Linux Mint 18 with the exception of upgrading the kernel to 4.4.0-38-generic. Everything was fine on Mint 17.3. Let me know if you need any more information, I'd really like to see this fixed.

empyreanx avatar Oct 03 '16 05:10 empyreanx