The first issue Iis in Webmin (and Virtualmin as well), the System information does not display the system information correctly. The CPU and Memory information is incorrectly output. The CPU shows resource usage up into the thousands percentages and the Memory shows consumption ranging from accurate measurement to inaccurate measurement (or at least it seems to look wrong according to readings acquired via CLI in FreeBSD).
The second issue is that while using ZFS on FreeBSD with Webmin, we cannot set quotas because the ZFS filesystem isn't recognized by default. We can't select which filesystem moutn point we want to set quotas on. The only mount point we can configure is the swap (Virtual Memory).
On Tuesday, December 12, 2017, 3:03:35 PM GMT-8, Jaret ootws@users.sf.net wrote:
[bugs:#5061] Webmin & ZFS on FreeBSD (Issues)
Status: open
Group: 1.860
Labels: ZFS Disk and Network Filesystems quota System Information
Created: Tue Dec 12, 2017 11:03 PM UTC by Jaret
Last Updated: Tue Dec 12, 2017 11:03 PM UTC
Owner: nobody
Attachments:
The first issue Iis in Webmin (and Virtualmin as well), the System information does not display the system information correctly. The CPU and Memory information is incorrectly output. The CPU shows resource usage up into the thousands percentages and the Memory shows consumption ranging from accurate measurement to inaccurate measurement (or at least it seems to look wrong according to readings acquired via CLI in FreeBSD).
The second issue is that while using ZFS on FreeBSD with Webmin, we cannot set quotas because the ZFS filesystem isn't recognized by default. We can't select which filesystem moutn point we want to set quotas on. The only mount point we can configure is the swap (Virtual Memory).
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/webadmin/bugs/5061/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Bugs:
#5061Last edit: Jaret 2018-03-13
You might want to try upgrading to Webmin 1.870, which fixes this CPU issue.
Updated issue is resolved. You may close this bug report. Thanks, jamie.
I just noticed this ticket was left open. Might want to close it since it's been fixed.