dotfiles/systemd/user/polybar@.service

[Unit]
Description=Polybar
Requires=graphical-session.target
After=graphical-session.target pulseaudio.socket i3.service

[Service]
ExecStart=/usr/bin/polybar --reload --log=warning %i
ExecReload=/usr/bin/polybar-msg cmd restart -p $MAINPID
Restart=always
Slice=session.slice

[Install]
WantedBy=desktop.target
systemd: launch i3 and user programs with systemd 2020-03-21 21:27:43 +00:00			`[Unit]`
			`Description=Polybar`
			`Requires=graphical-session.target`
systemd: polybar wait for i3 This should ensure that the IPC socket to get i3 workspaces works on polybar startup In reality this doesn't help because systemd marks the service as active before the socket file is created, so startup is still racy 2020-03-21 23:35:09 +00:00			`After=graphical-session.target pulseaudio.socket i3.service`
systemd: launch i3 and user programs with systemd 2020-03-21 21:27:43 +00:00
			`[Service]`
			`ExecStart=/usr/bin/polybar --reload --log=warning %i`
polybar: use 'polybar-msg cmd restart' to reload This is technically more of a restart than a reload, but it's the closest thing without actually restarting the main pid. Signed-off-by: Joe Groocock <me@frebib.net> 2020-08-10 20:26:16 +00:00			`ExecReload=/usr/bin/polybar-msg cmd restart -p $MAINPID`
systemd: launch i3 and user programs with systemd 2020-03-21 21:27:43 +00:00			`Restart=always`
systemd: assign default slices to user services As per recommendations in the systemd documentation, assign session, app or background slice allocations to the standard user services: https://github.com/systemd/systemd/blob/master/docs/DESKTOP_ENVIRONMENTS.md#pre-defined-systemd-units Signed-off-by: Joe Groocock <me@frebib.net> 2020-08-23 00:16:54 +00:00			`Slice=session.slice`
systemd: launch i3 and user programs with systemd 2020-03-21 21:27:43 +00:00
			`[Install]`
			`WantedBy=desktop.target`