You can also use systemd-cat to pipe the output of any command directly into the journal. For example: ls -l / | systemd-cat -p info -t my-script will run the command and log its output with an "info" priority and the identifier "my-script".

Unfortunately newer init systems like systemd have become increasingly complex to handle more desktop-focused requirements. Here’s a list of systemd APIs: does having 100s of public API functions and commands inspire confidence in its reliability?

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.

systemd 为什么会有那么大的争议？

The following steps will help you to get to a working systemd/user configuration:

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.

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:

Get off systemd, and enter the world of chroot.

Yes. That is a drop-in file. I think a leftover from the CentOS docker package. I just removed the file and it started working.

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.

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.

(daemon-reload won't reload/restart the services themselves, just makes systemd aware of the new configuration)

The advantage of the first method is that one easily overrides the complete unit, the default Container Linux unit is not parsed at all anymore.

After command, then we need to first reset the command withAfter= and then add our commands.

The systemd controversy seems to be a never ending saga among Linux users.

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.

Did my first Xubuntu 20.04 LTS last month: no (dependency) trouble at all to remove snap and its systemd tentacles...

I want the process list of a systemd unit - just like systemctl status $unitname does - but in machine-readable output, to look for specific processes.

systemctl show --no-page iptables \ | jq --slurp --raw-input \ 'split("\n") | map(select(. != "") | split("=") | {"key": .[0], "value": (.[1:] | join("="))}) | from_entries'

Unfortunately, it also gets the other properties, including bringing down the whole system when it crashes. This matters because systemd is complex

[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