When a file size increasing overtime, use truncate, but without changing anything to the file permission and other stuff that applied to it. Best with adding it to crontab.
truncate
crontab
-s is set limit file size e.g. 1024k
-s
$ truncate -s 1024k /var/log/kern.log
Unfortunately, this shortens the end of the file, which reduces its usability.
Luckily, you can set limit the file size.
When logging in, I am not interested in the beginning of the file, but mainly its end. Every time I cut it off, logging loses its meaning.
You are right. For user does not care about the logging but just want to reduce the file size (a couple of gigabytes). This is useful.
Some comments have been hidden by the post's author - find out more
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When a file size increasing overtime, use
truncate, but without changing anything to the file permission and other stuff that applied to it. Best with adding it tocrontab.-sis set limit file size e.g. 1024kUnfortunately, this shortens the end of the file, which reduces its usability.
Luckily, you can set limit the file size.
When logging in, I am not interested in the beginning of the file, but mainly its end. Every time I cut it off, logging loses its meaning.
You are right. For user does not care about the logging but just want to reduce the file size (a couple of gigabytes). This is useful.