Great Blue Heron

  • 16 Posts
  • 136 Comments
Joined 3 years ago
cake
Cake day: July 4th, 2023

help-circle


  • Great Blue Heron@lemmy.caOPtoPrivacy@lemmy.world•Fuck Virgin
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    EDIT: One other thought. If you and your wife have different phone hardware and especially if your hardware is very old, I believe that there’s hardware support required for WiFi calling support.

    My phone is actually newer. I know wifi calling works on my phone because I had it enabled with our previous carrier.















  • This is one of the things that frustrate me about Debian based systems. I know most distributions ship with lots of different tools to do the same job and you pick the one you like. But with something as fundamental as system timers it just feels wrong to me - when I want to change the timing of something I first need to figure out is the cron job real, or just a stub referring to the systemd timer, or visa versa.

    So for a while I had removed cron from all my systems and fully committed to timers. Now I’ve decided I don’t like systemd and gone fully the other way.

    I know it’s not that bad, but that’s the way my brain works - and I can remember getting really screwed up with some early Ubuntu systems.






  • What are you using to ship the logs to VL?

    That’s the reason I’m here asking about logging. I’m in the process of changing and wondering if I should switch it all up. I was using systemd-journal-remote, but I’m switching from Debian to Alpine so - no more systemd.

    you should start excluding them before they reach VL

    Now that confuses me. As I said in my original post - I had some preconceptions about centralised logging before I set it up, and having a single place to manage filters was certainly something I was hoping to get from it. Also any filtering would only be for reporting. I’d like to keep a full set of log data for potential problem analysis etc.