home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 21,406 of 21,939   
   The Natural Philosopher to All   
   Re: Cleaning up stale logs in Bookworm   
   14 Sep 25 18:22:39   
   
   MSGID: dont-email.me bd199faf   
   REPLY: dont-email.me c6e6e260   
   TZUTC: 1000   
   CHRS: CP437 2   
   REPLYADDR: tnp@invalid.invalid   
   REPLYTO: 3:633/280.2@fidonet UUCP   
   PID: Mozilla Thunderbird   
   TID: MBSE-FIDO 1.1.2 (Linux-x86_64)   
   RFC-Message-ID: <10a5u0f$1360o$8@dont-email.me>   
   RFC-From: The Natural Philosopher    
   RFC-References: <10a5c2h$tpdh$2@dont-email.me>   
   RFC-Organization: A little, after lunch   
   RFC-Content-Type: text/plain;   
   RFC-Content-Transfer-Encoding: 7bit   
   RFC-Injection-Date: Sun, 14 Sep 2025 08:22:40 +0000 (UTC)   
   RFC-Cancel-Lock: sha1:UIROG/grlZeG4bL93ZeOE+XO/wM=   
   RFC-Content-Language: en-GB   
   RFC-In-Reply-To: <10a5c2h$tpdh$2@dont-email.me>   
   On 14/09/2025 04:16, bp@www.zefox.net wrote:   
   > Is there some utility that will truncate accumulated log   
   > file in Bookworm? I set up an 8GB microSD for a Pi2 and   
   > have ended up using it much longer than expected.   
   >    
   > It might not help, but a housecleaning utility seems like   
   > a good thing to know about in any case.   
   >    
   > Thanks for reading,   
   >    
   > bob prohaska   
   >    
      
   Umm.   
   Are these old style logs or the dreaded systemd?   
      
   I maintained a log/script  of how to get the best out of a pi Zero and    
   never ever write to its SD card...   
      
   echo  "tmpfs /var/ramlog tmpfs nodev,nosuid,noexec,nodiratime,size=25M    
   0 	0" >> /etc/fstab   
      
   # /var/ramlog is used  for everything except systemd. Logrotate keeps it    
   tidy.   
   # various entties that create log files have to be configured to dump    
   stuff in it.   
      
   ## fuck with shitsemd   
      
   sed -i "s/#Storage=auto/Storage=volatile/" /etc/systemd/journald.conf   
   sed -i "s/#RuntimeMaxUse=/RuntimeMaxUse=25M/" /etc/systemd/journald.conf   
   sed -i "s/#ForwardToConsole=yes/ForwardToConsole=no/"    
   /etc/systemd/journald.conf   
   sed -i "s/#ForwardToWall=yes/ForwardToWall=no/" //etc/systemd/journald.conf   
      
   #Using volatile storage puts it in /var/run/systemd  and /var/run is    
   created as a ram   
   # based file system by the operating system   
      
   Naturally systemd doesn't use logrotate.  Wheels must be constantly    
   reinvented, but RuntimeMaxUse=25M does most of what you want   
      
   --    
   "I guess a rattlesnake ain't risponsible fer bein' a rattlesnake, but ah    
   puts mah heel on um jess the same if'n I catches him around mah chillun".   
      
      
      
   --- MBSE BBS v1.1.2 (Linux-x86_64)   
    * Origin: A little, after lunch (3:633/280.2@fidonet)   
   SEEN-BY: 19/38 105/81 106/201 128/187 129/14 305 153/7715 154/110   
   SEEN-BY: 218/700 226/30 227/114 229/110 111 200 206 275 300 317 400   
   SEEN-BY: 229/426 428 470 616 664 700 705 266/512 291/111 292/854 320/219   
   SEEN-BY: 322/757 342/200 396/45 460/58 633/280 281 418 420 509 2744   
   SEEN-BY: 712/848 770/1 902/26 2320/105 5020/400 5075/35   
   PATH: 633/280 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca