A cranky biologist who means well. My hobbies include long walks off short piers and anything science related.

  • 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle

  • This is sad news. He was deeply influential and at the same time a somewhat obscure author. At least, in my experience, he didn’t have the name recognition other - dare I say lesser - authors had.

    One lesson I learned as a young person from reading A Fire Upon the Deep was to never believe anything just because it was on the internet. That alone makes his legacy worth remembering.




  • It’s great as a mental prosthetic. When I am tackling a new complex topic like say a new cloud platform I’m learning, i can test my understanding of the implications of a change to the console settings. I tell it what i think and ask it to check my understanding. Really speeds up my learning, but I don’t rely on it exclusively. I will write my own dang emails, thank you.









  • meyotch@slrpnk.nettoLinux@lemmy.mlSystemd timer unit
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 months ago

    Your systemd file looks ok, but I think it’s doing exactly what you are telling it.

    The solution may lie in the backup.service. Is that code you can modify? The OnCalendar=weekly doesn’t specify when in the week the service should run so that config may be vague.

    If I understand the desired function here, you will need the service up all the time. It will just wait politely and occasionally run the specific backup script. It’s up to the backup script to determine when the last backup was made and either exit early because it hasn’t been a week or run the backup and reset a flag file.

    At least that’s the approach I would take. Systemd is a very vigilant, but very stupid, service manager. It just watches and triggers services based on just a few criteria. Any logic more complex needs to go in the service itself.


  • Not much love here for the Pi Zero W. I love them for being so flipping cute. I have a couple I use when I am learning a new system admin tool or service and I need to be able to let it run undisturbed to observe stability and function.

    Lately I am learning MQTT so am using one as a broker to manage some homemade smart devices.

    If I can ever find one in stock, i want a couple of Zero 2 for similar projects that would benefit from the extra oomph.




  • That was my intuition, based mostly on the typical behavior of allow/block lists generally. Thank you.

    As I understand it, the best way to promote small instances is to have users from other instances subscribe and contribute. This makes the communities visible on the subscribers instance so more people will see it.

    Even small instances have to have something interesting enough to attract subscribers, there’s no substitute for interesting content.

    OP, I understand and endorse the desire to help elevate the smaller instances, so it’s a worthwhile discussion the post has stimulated. Thanks!


  • I ask this partly as a question and partly to start a discussion I hope educates me on these details. I host a small instance too and definitely want to know these things better.

    Is it necessary to add an instance to the allowed list? If federation is enabled, isn’t an instance ’allowed’ by default? Wouldn’t subscribing to communities on the small instances be of better benefit?

    Thanks to anyone who understands the mechanics at play here and is willing to break it down.