Difference between revisions of "Limit the size of .log files & the journal/ru"

Created page with "Такие приложения, как Apache, MySQL, Cups и другие, помещают скрипты в каталог /etc/logrotate.d для управления с..."
(Created page with "== /etc/logrotate.conf и /etc/logrotate.d ==")
(Created page with "Такие приложения, как Apache, MySQL, Cups и другие, помещают скрипты в каталог /etc/logrotate.d для управления с...")
Line 197: Line 197:
== /etc/logrotate.conf и /etc/logrotate.d ==
== /etc/logrotate.conf и /etc/logrotate.d ==


The logrotate.conf configuration file largely dictates logrotate's behaviour, it holds global settings, but most of the work that logrotate does is via script files stored in the '''/etc/logrotate.d''' directory, which take precedence over the global settings held in logrotate.conf.
Файл конфигурации logrotate.conf в значительной степени определяет поведение logrotate - он содержит глобальные настройки, но большая часть работы, которую выполняет logrotate, осуществляется с помощью файлов сценариев, хранящихся в каталоге '''/etc/logrotate.d''', которые имеют приоритет над глобальными настройками, содержащимися в logrotate.conf.


Applications such as Apache, MySQL, Cups & others, put scripts into the /etc/logrotate.d directory to manage their log files.
Такие приложения, как Apache, MySQL, Cups и другие, помещают скрипты в каталог /etc/logrotate.d для управления своими лог-файлами.


If you manually run the command '''sudo logrotate''', you will be presented with its usage template. logrotate needs you to specify the path to the script that you want it to use, including the logrotate.conf file which one may think due to its name would be automatically read, it is not.
If you manually run the command '''sudo logrotate''', you will be presented with its usage template. logrotate needs you to specify the path to the script that you want it to use, including the logrotate.conf file which one may think due to its name would be automatically read, it is not.
translator
11,555

edits