Wherever possible, the applications in your stack should be managed by your server’s init system, which on most modern Linux distributions including Rocky Linux is systemd. Despite this, one of the most common reasons for not having a good update strategy in place is being concerned about how your server will behave after being restarted. Linux package managers are designed to run non-disruptively in the background so that necessary maintenance does not come with any additional overhead. Step 1 – Following Best Practices for Application ManagementĪ fundamental part of configuring your server for automatic upgrades is ensuring that all of the applications running on the server are able to restart correctly after unplanned downtime or a reboot. You can learn more about how to set up a user with these privileges in our Initial Server Setup with Rocky Linux 9 guide. A Rocky Linux 9 server and a non-root user with sudo privileges.Live kernel patching, and other best practices around kernel updates.Configuring automatic updates for most of the packages and libraries running on your machine.Testing graceful reboots following best practices for application management, to minimize any complications from maintenance updates.If you’re doing your own server administration, it can be quite disruptive and error-prone to patch all of your environments manually. There are a number of tools and configurations that you can apply to most Rocky Linux servers beyond what is configured for you automatically. Just as with network security hardening, there are many steps you can take to ensure your servers will continue to work securely without future intervention. In this tutorial, you’ll explore some best practices for keeping your Rocky Linux 9 server stack up to date.
0 Comments
Side note: Every PWM fan can also be DC-controlled, it's just a slightly worse method of controlling it. But in this example, you'd want your PWM fans on the CPUFAN headers, if possible. On more expensive board models, all the fan headers should be able to control fans with both methods. "NC" means Not Connected, so the manufacturer didn't implement PWM control on those headers, presumably for cost-saving. The SYSFAN headers can only control the fan speed via DC voltage, despite having a 4-pin fan header. The CPUFAN headers can control the fan speed via PWM signal or DC voltage (depending on the fan and which control method you select in the BIOS). So pay extra attention to that.īut that's easy to notice in the BIOS - when you just can't control a certain 4-pin fan with a PWM signal and instead only have DC (voltage) control available. Some motherboard models may only allow DC control for some of the fan headers, even though they can all be 4-pin headers. So for each fan, you have to select the right fan control method: DC for a 3-pin fan or PWM for a 4-pin fan. Side note: The "RPM Speed Signal" pin (rotations per minute) in the picture is telling the motherboard at which speed the fan is spinning, it is not controlling the fan. With a PWM-controlled fan, the board powers it with a steady 12V, and the fan speed is controlled through the fourth pin via a PWM signal. With a DC-controlled fan, the fan speed is regulated by the board powering it with lower or higher voltages (say, between 3V and 12V) instead of steady 12V. A 4-pin plug means it's PWM (pulse width modulation) controlled. A three-pin plug means the fan is DC (= direct current) voltage-controlled. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |