One of the many changes with the recent Ubuntu 22.04 LTS release was enabling systemd-oomd by default as the out-of-memory daemon that can kill processes when under memory pressure. Unfortunately, for some users this has led to a poor desktop experience with finding their applications being unexpectedly killed. Ubuntu developers are now discussing how to improve this OOMD handling. . Various bug reports and other issues have turned up of user applications being killed "too frequently" such as the Chrome web browser and generally without notice or the user even being unaware they are under memory pressure. Ubuntu developers are now trying to figure out how to best handle the out-of-memory daemon's behavior moving forward. Among the items being looked at are to increase the "SwapUsedLimit" that controls the threshold for memory usage and swap usage, being more selective in its "ManagedOOMSwap" configuration, not enabling swap kill at all, or possibly but less likely is increasing the swap size on Ubuntu from its current 1GB default. The link for this article located at Phoronix is no longer available. . Explore the strategies Ubuntu is implementing to enhance the functionality of systemd-oomd, particularly in response to the continuous terminations faced by user applications.. Ubuntu Out-Of-Memory,Systemd Management,User Experience Improvement,Daemon Optimization. . LinuxSecurity.com Team
If you're still running inetd, it's time to move on. Either xinetd or tcpserver offer superior security and control. We're going to look at tcpserver. Note that there is one limitation: it manages only tcp. If you're using UDP or rpc services, tcpserver alone will not do the job. In that case, xinetd is the way to go.. . .. If you're still running inetd, it's time to move on. Either xinetd or tcpserver offer superior security and control. We're going to look at tcpserver. Note that there is one limitation: it manages only tcp. If you're using UDP or rpc services, tcpserver alone will not do the job. In that case, xinetd is the way to go. The (in)Famous DJB tcpserver is part of the ucspi-tcp suite of tools by none other than the famous, and infamous, Daniel J. Bernstein. Professor Bernstein seems to inspire strong passions in the tech community; some refuse to use his software because they do not like the author. Other objections are that his programs install themselves in non-standard file locations, and that he keeps too tight a grip on the code. Personality issues aside, I find that his programs are lean, fast, secure, and worthy on their own merits. A special item of note is Professor Bernstein led the suit against the United States Government against export controls on encryption software, and won. DJB's security model is based on a zero-trust premise. His programs don't even trust themselves- each function is isolated from other parts of the program. They run in user accounts with restricted rights; services that require root access are as restricted and limited as possible. Any successful intrusion will be severely limited, if an intruder can get in at all. The link for this article located at CrossNodes is no longer available. . Tcpserver provides significant advantages over inetd for managing TCP services, focusing on security, isolation, resource controls, and improved logging capabilities. Tcp Server Management, Xinetd Alternative, Daemon Security, Network Control. . LinuxSecurity.comTeam
Get the latest Linux and open source security news straight to your inbox.