REPLY: 2:423/39 5fdf0c53   
   MSGID: 2:250/1@fidonet 5fdf5add   
   CHRS: UTF-8 2   
   TZUTC: 0000   
   TID: MBSE-FIDO 1.0.7.17 (GNU/Linux-x86_64)   
   Hello Karel!   
      
   Sunday December 20 2020 09:25, you wrote to Kai Richter:   
      
   ....   
    > Actually fighting that idea of journalctl. OK, nice, new, complex,   
    > holistic...   
      
    > There is usualy one need: to keep logs for certain amount of time   
    > (based on SLA, based on law, etc.) Looks to me that design focused to   
    > zillion switches how to influence/keep disk space, but how to achieve   
    > that I have 100% of time frame logged is not so easy. Shall I try to   
    > calculate disc space? Shall I rather put there all space to be sure?   
      
    > From man: "...Normally, time-based deletion of old journal files   
    > should not be required as size-based deletion with options such as   
    > SystemMaxUse= should be sufficient to ensure that journal files do not   
    > grow without bounds..."   
      
   Look at logrotate which is the normal product to control journal files in   
   /var/log   
      
      
      
   Vincent   
      
   --- Mageia Linux v7.1 X64/Mbse v1.0.7.17/GoldED+/LNX 1.1.5-b20180707   
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)   
   SEEN-BY: 1/123 3/50 15/0 16/101 19/36 20/4609 25/0 21 90/1 105/81   
   SEEN-BY: 106/201 116/18 120/331 340 123/131 140 128/2 153/757 7715   
   SEEN-BY: 218/700 222/2 226/30 227/114 702 229/101 424 426 452 550   
   SEEN-BY: 229/616 664 1016 230/150 152 240/1120 5832 249/206 317 400   
   SEEN-BY: 250/0 1 2 4 5 8 32 261/38 100 1466 263/0 266/512 267/155   
   SEEN-BY: 275/100 280/464 282/1031 1056 291/100 111 292/854 317/3 320/119   
   SEEN-BY: 320/219 322/757 340/400 341/66 342/200 396/45 633/0 267 280   
   SEEN-BY: 633/281 384 410 412 509 640/1321 1384 712/620 848 770/1 801/161   
   SEEN-BY: 801/189 2320/105 3634/12 5020/715 1042   
   PATH: 250/1 261/38 712/848 633/280 229/426