Skip to content

systemd: remove outdated config for syslog #499

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

systemd: remove outdated config for syslog #499

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92d7524
systemd: use StandardError=journal instead of the deprecated Standard…
erictapen Oct 1, 2021
d5c2f65
systemd: Drop syslog.target, as it doesn't exist anymore
erictapen Oct 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions Systemd.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,6 @@ Create a systemd service file (you can save it as /etc/systemd/system/emperor.uw

[Unit]
Description=uWSGI Emperor
After=syslog.target

[Service]
ExecStart=/root/uwsgi/uwsgi --ini /etc/uwsgi/emperor.ini
Expand All @@ -32,7 +31,7 @@ Create a systemd service file (you can save it as /etc/systemd/system/emperor.uw
Restart=always
KillSignal=SIGQUIT
Type=notify
StandardError=syslog
StandardError=journal
NotifyAccess=all

[Install]
Expand Down Expand Up @@ -87,7 +86,7 @@ If you want to allow each vassal to run under different privileges, remove the `
Logging
*******

Using the previous service file all of the Emperor messages go to the syslog. You can avoid it by removing the ``StandardError=syslog`` directive.
Using the previous service file all of the Emperor messages go to the journal. You can avoid it by removing the ``StandardError=journal`` directive.

If you do that, be sure to set a ``--logto`` option in your Emperor configuration, otherwise all of your logs will be lost!

Expand Down Expand Up @@ -174,7 +173,6 @@ app will run under its own user.

[Unit]
Description=%i uWSGI app
After=syslog.target

[Service]
ExecStart=/usr/bin/uwsgi \
Expand All @@ -185,7 +183,7 @@ app will run under its own user.
Restart=on-failure
KillSignal=SIGQUIT
Type=notify
StandardError=syslog
StandardError=journal
NotifyAccess=all

Now, adding a new app to your system is a matter of creating the appropriate
Expand Down