REPLY: 2:240/77 5fce8eaf   
   MSGID: 2:423/39 5fdf0c53   
   CHRS: CP895 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 0.62   
   Hello Kai!   
      
   07 Dec 20 20:52, you wrote to me:   
      
    KR> Yes. Stop wasteing our time and let's do something useful.   
      
    KR> For example teach me if it's wasteing or wasting? I do write looking   
    KR> and watching but with "e" if it's boeing. What's the rule of that??   
      
   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..."   
      
   Looks like I am not normal ;-)   
      
   Karel   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: Plast DATA (2:423/39)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 123/131 124/5016 154/10   
   SEEN-BY: 203/0 221/1 6 242 360 226/30 227/114 702 229/101 424 426   
   SEEN-BY: 229/452 550 616 664 1016 240/5832 249/110 206 317 400 280/464   
   SEEN-BY: 280/5003 288/100 292/854 8125 310/31 317/3 322/757 342/200   
   SEEN-BY: 396/45 420/33 333 421/79 83 423/36 39 81 120 121 633/280   
   SEEN-BY: 712/848 770/1 2452/250 5020/545   
   PATH: 423/39 81 221/1 280/464 229/101 426