/explore
|
You are here 
|
www.schakko.de | ||
| | | | |
bijanebrahimi.github.io
|
|
| | | | | ||
| | | | |
artemis.sh
Linux won't sleep on this motherboard out of the box. I have a rev1.1 motherboard running BIOS version F17b. No idea if this applies to rev1.2. There's a workaround you can do which is to disable PCIe wakeup on GPP0 (GPP bridge to the m.2 NVMe drives): echo GPP0 | sudo tee /proc/acpi/wakeup. To make this persistent you need to run this command at boot. I do not know why it is like this. systemd/openrc methods to run this at boot: |
|
| | | | | ||
| | | | |
willhaley.com
iperf3 is useful for testing the network throughput of your local network. It can help to indicate network bandwidth of individual nodes on your LAN. Do you have one computer that seems perpetually slow? Then iperf3 may be able to confirm this potential issue. A WAN speedtest service like Google's will not necessarily indicate the speed of individual nodes on your LAN. Rather, it is better suited to testing the throughput from your home to the public Internet. |
|
| | | | | ||
| | | | |
www.nageshdn.com
Cron utility in Linux has been helpful to schedule tasks to run at a scheduled time. A few of the disadvantages of cron are If Instance/server is not available/down at the cron schedule, cron doesn't run those tasks until the next event is triggered If the cron task need to run other tasks after running the main task at the scheduled time, there are only hacks to create this dependency If the cron task needs to run within a given time interval to avoid running at the same time If a cron task needs to run after an event, such as 3 minutes after the system restarted. Cron doesn't support this functionality To check the status of the last cron task to see if it ran/failed with logs |
|
| | | |||
