search for: throtting

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance

On Sun, Aug 9, 2020 at 1:40 PM Chuck Campbell <campbell at accelinc.com> wrote: > ... > dnf copr enable abn/throttled > dnf install -y throttled > > but I get this output: > Error: > Problem: conflicting requests > - nothing provides python3-configparser needed by throttled0.7-1.x86_64 > > I have no guess what to do about this. Well, that dependency is

I am keen to look at Rcgi as I want to put up some simple bits of R to do prescribed tasks on HTML form input. Rweb is overkill and worryingly flexible for what I want and it sounds as if Rcgi is more what I need. However, I can't get any of the URLs I've found for it to work over the last few days. Does anyone have a recent copy they could Email me or a working URL for it? TIA,

Hi, guys. I want to change block I/O throttle using 'virsh blkdeviotune' with vm not running, it reported an error: # virsh blkdeviotune instance-000000dc /dev/loop0 --total-bytes-sec 20000000 --total-iops-sec 20 --config error: Unable to change block I/O throttle error: unsupported configuration: block I/O throttling not supported with this QEMU binary I can do this when the vm is

Hi ZFSers, I''ve been working on merging the Joyent arcstat enhancements with some of my own and am now to the point where it is time to broaden the requirements gathering. The result is to be merged into the illumos tree. arcstat is a perl script to show the value of ARC kstats as they change over time. This is similar to the ideas behind mpstat, iostat, vmstat, and friends. The current

hello list (and martin) ;x i have now composed my final(?) policy routing design. the goals i had when beginning with this, for you that have not follow mine and martins thread, was to 1) only let 192.168.1/24 to see all routes, 2) not route between defined networks, except to and from 192.168.1/24 and 3) not defined networks should only be able to reach 192.168.1/24. this might sound simple.