• Ignotum@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 months ago

    was i supposed to find that out by myself

    Just do what i did, wait for someone to post about it on lemmy then learn about it from that
    That’s actually how i learned most of the things i know

  • Lucy :3@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Though you still have to suspend by yourself when you’re done.

    Does

    ExecPost=systemctl suspend
    

    work ?

    • Björn Tantau@swg-empire.deOP
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Probably.

      But what if the timer triggered during normal operation? Then your computer would suddenly suspend on its own and you wouldn’t know why.

      I’ve already made a feature request to only run when the system is suspended.

      Until then I’ll look at when the system woke up and if that was less than a minute ago turn off the display and suspend after everything is done.

  • gazter@aussie.zone
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Linux newb here. What does this mean? My knowledge of systemd is that it is responsible for things like mounting disks and running networking. So does this mean I can ask systemd to grab a new IP address every x hours, even if the machine is asleep?

    • rtxn@lemmy.worldM
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months ago

      Systemd is a collection of low-level system utilities. Its primary responsibility is managing services and serving as the init process (PID 1, the first userspace process started by the kernel), but it also has other components, like systemd-boot (a boot loader and GRUB alternative), journald (system logging), networkd (network interface management), resolved (DNS resolver), or udevd (manages device files in /dev).

      People tend to vilify systemd because it is maintained by Red Hat, a company with many controversies, and a pariah among the more extreme FOSS enthusiasts; and because it’s seen as bad practice to have a single entity be responsible for so many low-level system components.

      Note: the -d suffix is not exclusive to systemd things. It simply marks the program as a daemon, a long-running background process that provides some kind of service. For example, sshd (SSH server) or httpd (Apache server on some distros) are not parts of systemd.

      To answer your question: not really. As far as I know, the network interface won’t have an IP address unless the computer is turned on. If you use a timer (or any other method for that matter) to power on the computer, it will request an address from DHCP as soon as the interface is brought up (unless it has a static address).

      A more practical application would be scheduling long, unattended tasks, like updates or making backups.