47 Matching Annotations
  1. Jan 2024
    1. Because we use systemd for most of our service management, these stdout/stderr streams are generally piped into systemd-journald which handles the local machine logs. With its RateLimitBurst and RateLimitInterval configurations, this gives us a simple knob to control the output of any given service on a machine. This has given our logging pipeline the colloquial name of the “journal pipeline”, however as we will see, our pipeline has expanded far beyond just journald logs.

      I did not expect to see journald being used as the basic building block

  2. Dec 2022
  3. Aug 2022
  4. Jan 2022
  5. Dec 2021
  6. Mar 2021
    1. The following steps will help you to get to a working systemd/user configuration:
    2. I consider systemd/user as a good alternative for dex's autostart functionality and switched to it recently. In particular, systemd solves the issue of dex losing control over the started processes which causes processes to live longer than the X session which could cause additional annoyances like reboots taking a lot of time because the system is waiting for the processes to terminate.
  7. Feb 2021
    1. Systemd targets are reached once and do not fire again when the connection state changes. Depending how your network is managed there are a couple of options:

      Alternatives to react to network-changes in various linux setup: systemd, NetworkManager, netcl, wicd

    1. About network-activation targets & events, but does not detect e.g. "airplane-mode" :-( (referred by man-pages)

  8. Jan 2021
    1. Reload the systemd manager configuration. This will rerun all generators (see systemd.generator(7)), reload all unit files, and recreate the entire dependency tree. While the daemon is being reloaded, all sockets systemd listens on behalf of user configuration will stay accessible.
    1. In case you changed something in the [Install] directive, you may need to run sudo systemctl reenable YOURUNITFILE in order to recreate the symlinks in the .target directories.
    2. (daemon-reload won't reload/restart the services themselves, just makes systemd aware of the new configuration)
    1. Its not too complicated but it is an annoyance. I want /etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf, /etc/rc.local and all the standard stuff to work. The heavy lifting is done in the kernel. All they need to do is leave it alone. Its getting harder to make Ubuntu behave like Linux.
    2. Did my first Xubuntu 20.04 LTS last month: no (dependency) trouble at all to remove snap and its systemd tentacles...
  9. Nov 2020
    1. systemctl show --no-page iptables \ | jq --slurp --raw-input \ 'split("\n") | map(select(. != "") | split("=") | {"key": .[0], "value": (.[1:] | join("="))}) | from_entries'
  10. Dec 2019
    1. Unfortunately, it also gets the other properties, including bringing down the whole system when it crashes. This matters because systemd is complex
  11. Nov 2019
  12. Sep 2019
  13. Mar 2019
  14. Oct 2018
  15. Sep 2018
  16. May 2016
    1. [Service] ExecStart=[node binary] /home/srv-node-sample/[main file] Restart=always StandardOutput=syslog StandardError=syslog SyslogIdentifier=node-sample User=srv-node-sample Group=srv-node-sample Environment=NODE_ENV=production [Install] WantedBy=multi-user.target