VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling 2022-07-07T08:07:55+00:00 2022-07-07T08:07:55+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2022-07-06T17:35:11+00:00 urn:sha1:52ce659509022807c4a38fcb791abd325f3e8b00 After discussion with @zsdc this was decided the better long term fix * Removes hourly logrotate cron in favour of systemd timer override 2022-07-06T15:43:01+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2022-07-06T15:43:01+00:00 urn:sha1:9b6d03061b6fcb51d874b91f6bea4bf23cdab3bf 2022-03-07T16:20:53+00:00 zsdc taras@vyos.io 2022-03-07T16:20:53+00:00 urn:sha1:ebb524702e1cd60a74b00727b7bd24d375648c78 * Removed `/var/log/auth.log` and `/var/log/messages` from `/etc/logrotate.d/rsyslog`, because they conflict with VyOS-controlled items what leads to service error. * Removed generation config file for `/var/log/messages` from `system-syslog.py` - this should be done from `syslom logs` now. * Generate each logfile from `system syslog file` to a dedicated logrotate config file. * Fixed logrotate config file names in `/etc/rsyslog.d/vyos-rsyslog.conf`. * Added default logrotate settins for `/var/log/messages` 2022-03-05T08:40:32+00:00 Christian Poessinger christian@poessinger.com 2022-03-05T08:40:32+00:00 urn:sha1:2c94c3ec72a559de405b29b4399250db3085717e 2021-11-09T17:12:35+00:00 zsdc taras@vyos.io 2021-11-09T16:46:10+00:00 urn:sha1:14e3b26ff5ffce9ae19050645b0efc6c4725880a The systemd unit for atop service is changed, so the log file name and location will be always the same. It also adds the logrotate configuration to conditionally rotate a log file. Hardcoded values: - maximum log file size: 10 MB - maximum count of files: 10 These values can be easily changed within the `/etc/logrotate.d/vyos-atop`, no additional configuration is required. Rotation will be done hourly, if necessary, according to `/etc/cron.hourly/vyos-logrotate-hourly`. This change has two benefits: - rotation strategy control can be done via logrotate, and can be exposed to CLI now; - the total size of all logs is now controlled more aggressively, so the chance to get a situation when atop logs took all the space on a drive is significantly lower. Also, if this will be necessary, rotation may be done even each minute what reduces risks related to logs size even more.