XPost: uk.comp.os.linux   
   From: dan@djph.net   
      
   On 2025-09-10, Mike Scott wrote:   
   > On 10/09/2025 10:37, Dan Purgert wrote:   
   >> I'm not sure what you mean here.  "Logrotate" is a tool that exists.   
   >   
   > logrotate assumes the target can close and re-open its log.   
      
   By default, sure; but there are options to deal with it.   
      
      
   copytruncate   
     Truncate  the original log file to zero size in place after cre-   
     ating a copy, instead of moving the old log file and  optionally   
     creating  a new one.  It can be used when some program cannot be   
     told to close its logfile and thus might continue  writing  (ap-   
     pending) to the previous log file forever.  Note that there is a   
     very small time slice between copying the  file  and  truncating   
     it,  so  some  logging  data might be lost.  When this option is   
     used, the create option will have no effect, as the old log file   
     stays  in place.  The copytruncate option allows storing rotated   
     log files on the different devices using olddir directive.  The   
     copytruncate option implies norenamecopy.   
      
      
      
      
   --   
   |_|O|_|   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)