TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 61eab2f7   
   REPLY: 3:770/100 7fa72316   
   Hi Dan,   
      
   On 2022-01-22 02:13:59, you wrote to me:   
      
    Wv>> On 2022-01-21 12:58:40, you wrote to me:   
    Wv>>   
    Wv>>  Wv>> Mine is run on system startup as a systemd.service. So there is   
    Wv>> no   
    Wv>>  Wv>> console to look at. If I want to see what's going on I have a   
    Wv>> look a   
    Wv>>  Wv>> the log...   
    Wv>>   
    Wv>>  DC> Does `journalctl` not show useful data from the output   
    Wv>>  DC> of binkd?   
    Wv>>   
    Wv>> Forgot about that one. I never use it... But indeed you can have a   
    Wv>> look at it, but is it usefull?   
      
    DC> I dunno...I don't run binkd.  I've found it very useful for   
    DC> seeing what Direwolf is doing (or not doing) on my packet   
    DC> radio station, though. YMMV.   
      
   When you use the -q (quiet) option for binkd, like I do, it isn't very   
   talkative on the console. But the things that still show up in journalctl,   
   might be interesting in that case...   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10   
   SEEN-BY: 203/0 218/840 220/70 221/0 226/17 30 227/114 229/110 200   
   SEEN-BY: 229/307 317 424 426 550 664 700 240/5832 249/206 250/5 8   
   SEEN-BY: 266/512 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25   
   SEEN-BY: 301/1 305/3 310/31 317/3 320/219 322/757 341/234 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 100 340 772/210   
   SEEN-BY: 772/220 230 2452/250   
   PATH: 280/464 770/1 317/3 229/426