automation

Cron

botond published 2024/03/05, k - 10:40 time
This encyclopedia entry provides a detailed introduction to the Cron system, the basic Linux tool for automating scheduled tasks. The description covers the structure of Cron, including the role of the background daemon and the crontab files containing the tasks. We will get acquainted with the Unix roots of the system and the development of modern implementations. The article places great emphasis on a detailed description of the crontab syntax, introducing the use of timing fields, special characters, and user-friendly aliases such as @daily. We distinguish between user-level and system-level cron job management, covering the use of the /etc/crontab and /etc/cron.d directories. The description also provides practical advice on avoiding the most common pitfalls, such as problems with the PATH environment variable and the correct handling of command output. Finally, we will introduce the role of Anacron, which ensures reliable execution of tasks on machines that are not constantly running.

Perfect server: Debian 11 (Bullseye) v1.0

botond published 2022/12/13, k - 07:08 time
In this description, we will create a newer, Debian 11 (Bullseye) version of the perfect server. Unlike the previous perfect server installations, this time we will not do this with lengthy package installations and configurations, but with the help of an automation script, which the developers of ISPConfig have put together to facilitate the preparation of the server. The script has been available for some time, with the help of which it can be used not only on the Debian 11 (Bullseye) operating system, but also on the Debian 10 version, as well as on Ubuntu 20.04 and Ubuntu 22.04 systems. I automated the components of the perfect server.

How to automatically clean PHP session files left in the tmp directories of web accounts in an ISPConfig server environment

botond published March 2021, 03, Thu - 04:11 time
PHP sessions are global variables that transmit data stored during web visits across multiple pages, i.e., they are not lost when moving from one page to another. PHP accomplishes this by assigning unique IDs to visits (sessions) and creating files in the server-side file structure associated with those IDs in which it stores the data required for the session. The system places these files in a specific directory, usually tmp, which is normally deleted by the garbage collector after a specified time. However, the situation is sometimes not so obvious. This is because if the PHP environment on the server changes, the garbage collector may not be able to delete these obsolete, unnecessary session files. In this description, we will look at how we can use our own solution to ensure that these session files are deleted when the default cleaning system cannot remove them.