5 ms·

Why does the complexity of the rest of systemd matter when comparing the implementation of this feature? What would you say is wrong with RandomizedDelaySec?

by ratorx 3y ago

mekster 3y ago
UI is too complicated to type some word concatenated keyword than being visually intuitive.
- vbezhenar 3y ago
  On the other hand I wouldn't be able to understand what the hell is this cron string. I actually have no idea about cron format despite the fact that I used it multiple times. I have to read man every time I use it. Also different software implements it differently. [Timer] OnCalendar=daily RandomizedDelaySec=12h might take few more seconds to type, but it's definitely readable without any additional documentation.
  - panzi 3y ago
    The option says Sec but the value says h? What does that mean?
    - rjh29 3y ago
      Sec is a standard suffix for time values, anything ending with Sec accepts a value in seconds. 12h is shorthand for 'the number of seconds in 12 hours'
      - Gud 3y ago
        Standard where? I have never seen this before and I’ve been reading *nix configuration files for 20+ years
        rjh29 3y ago
        Standard within systemd (i.e. consistent).
      - gkbrk 3y ago
        It's standard to say 12h and expect this to read as 43200? Sounds like a lousy standard if the correct way to use it is to say "I want to delay by 12 hour seconds". What is even "12 hour seconds"?
        rjh29 3y ago
        In our code at work we have constants like HOUR=3600 and RESTART_TIME_SECS = 6 * HOUR. It makes sense to me. If it doesn't for you, feel free to use something else I guess.
        unethical_ban 3y ago
        Makes sense once you know it. "Sec" suffix indicates time and implements a default of seconds, where a suffix to the value indicates a change in unit. It would be like Asking "Memory Allocation(MB)" but accepting "12G" for 12 GB.
    - justsomehnguy 3y ago
      > The arguments to the directives are time spans configured in seconds. Example: "OnBootSec=50" means 50s after boot-up. The argument may also include time units. Example: "OnBootSec=5h 30min" means 5 hours and 30 minutes after boot-up. https://www.freedesktop.org/software/systemd/man/systemd.timer.html https://www.freedesktop.org/software/systemd/man/systemd.tim... Ie seconds if no units specified.

Why does the complexity of the rest of systemd matter when comparing the implementation of this feature? What would you say is wrong with RandomizedDelaySec?

by ratorx 3y ago

Why does the complexity of the rest of systemd matter when comparing the implementation of this feature? What would you say is wrong with RandomizedDelaySec?

mekster 3y ago

UI is too complicated to type some word concatenated keyword than being visually intuitive.

vbezhenar 3y ago
On the other hand I wouldn't be able to understand what the hell is this cron string. I actually have no idea about cron format despite the fact that I used it multiple times. I have to read man every time I use it. Also different software implements it differently. [Timer] OnCalendar=daily RandomizedDelaySec=12h might take few more seconds to type, but it's definitely readable without any additional documentation.
- panzi 3y ago
  The option says Sec but the value says h? What does that mean?
  - rjh29 3y ago
    Sec is a standard suffix for time values, anything ending with Sec accepts a value in seconds. 12h is shorthand for 'the number of seconds in 12 hours'
    - Gud 3y ago
      Standard where? I have never seen this before and I’ve been reading *nix configuration files for 20+ years
      - rjh29 3y ago
        Standard within systemd (i.e. consistent).
    - gkbrk 3y ago
      It's standard to say 12h and expect this to read as 43200? Sounds like a lousy standard if the correct way to use it is to say "I want to delay by 12 hour seconds". What is even "12 hour seconds"?
      - rjh29 3y ago
        In our code at work we have constants like HOUR=3600 and RESTART_TIME_SECS = 6 * HOUR. It makes sense to me. If it doesn't for you, feel free to use something else I guess.
      - unethical_ban 3y ago
        Makes sense once you know it. "Sec" suffix indicates time and implements a default of seconds, where a suffix to the value indicates a change in unit. It would be like Asking "Memory Allocation(MB)" but accepting "12G" for 12 GB.
  - justsomehnguy 3y ago
    > The arguments to the directives are time spans configured in seconds. Example: "OnBootSec=50" means 50s after boot-up. The argument may also include time units. Example: "OnBootSec=5h 30min" means 5 hours and 30 minutes after boot-up. https://www.freedesktop.org/software/systemd/man/systemd.timer.html https://www.freedesktop.org/software/systemd/man/systemd.tim... Ie seconds if no units specified.