Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    Of course, one can challenge the whole idea of using logrotate in the first place, when (with suitable application of things like /dev/stderr if necessary) one can just do the task directly in the script. unix.stackexchange.com/a/340631/5132 unix.stackexchange.com/a/326166/5132 Commented Jan 17, 2020 at 12:39
  • Thanks, I'm at best a low-intermediate Linuxer. At this stage I'd just like to find a way of configuring logrotate so my disks don't get jammed up with monstrous log files. There's also the "right tools for the job" argument, which I'm not qualified to answer... although I assume logrotate is probably meant to do what it says on the tin. Commented Jan 17, 2020 at 12:54
  • Plus the other thing is, with rclone you set an option, --log-file... the process just carries on regardless, spewing out log messages. Do those other tools you reference run as cron jobs? (As I presume logrotate does...)? Commented Jan 17, 2020 at 12:59