-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cron worker with journalctl cleaner #2790
base: master
Are you sure you want to change the base?
Conversation
should we use a script instead? we need something to cleanup the autopilot and mavlink logs from time to time, too 🤔 |
0dc79ae
to
3a182ce
Compare
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
2afae41
to
276f59b
Compare
what you mean by script ? |
never mind, if we have cron working, we can just had other entries for cleaning different things |
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
yes, that the plan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea of adding a cron is interesting for our system, however, journalctl is a log manager that doesn't require user intervention: it has configurations like (1) log size, (2) free disk size, (3) rate limit, (4) compression, and it will vacuum automatically.
https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html
What is better, calling journalctl configuration command or working on journalctl configuration file/parameters, dealing with user custom configuration and identifying (based in the OS), which of the following files to change ? |
To me it adds extra complexity at the moment, what is the problem of the current approach ? |
(1) we are taking power from the administrator, and (2) we are reinventing the wheel instead of configuring a basic system tool. What I recommend is that when installing the system, we should overwrite (with a backup) |
Installation does not fix the problem for current BlueOS systems. |
Can't we install it if the file doesn't exist? |
By default this file comes from the OS. |
I'm working in an alternative solution. |
Helps #2328