This works for me, YMMV:/etc/systemd/system/screen.service[Unit]
Description=Detached screen session
After=network.target
[Service]
Type=oneshot
RemainAfterExit=yes
User=tomk
ExecStart=/usr/bin/screen -dm
[Install]
Wants=network.target
WantedBy=multi-user.target ~/.screenrc...
screen -t rtorrent 5 /usr/bin/rtorrent
...
tomk
https://bbs.archlinux.org/profile.php?id=1822
2013-03-
After boot-up process systemd starts agetty, but after 1--2 seconds additional messages are appeared:
How to avoid this?
I use Arch Linux, systemd 194.
$ grep '^[^#]' /etc/systemd/system/getty.target.wants/getty@tty1.service
[Unit]
Description=Getty on %I
Documentation=man:agetty(8)
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
Before=getty.target
Ignor
Hi, I am trying to write a systemd service that runs and completes before NetworkManager.service starts.I tried this:[Unit]
Description=Custom service test
Before=NetworkManager.service
[Service]
Type=oneshot
ExecStart=/usr/bin/echo Custom service test 1
ExecStart=/usr/bin/sleep 5
ExecStart=/usr/bin/echo Custom service test 2
[Install]
WantedBy=network.targetWhile the custom service does start,
Can I do This start up service below, there are no errors showing once run, but the server script below does not run!
ln /lib/systemd/aquarium.service aquarium.service
systemctl daemon-reload
systemctl enable aquarium.service
systemctl start aquarium.service
thanks
aquarium.service:
[Unit]
Description=Start aquarium server
[Service]
WorkingDirectory=/home/root/python/code/aquarium/
ExecStart
@dxxvi I have also been having issues with apache since I moved to systemd at the weekend.
I wanted to see if anyone else is using systemd --user as their user session. I have a few questions, but first I'll just describe what I've done./usr/share/xsessions/systemd.desktop[Desktop Entry]
Name=systemd
Exec=systemd --user
Type=XSessionThen, in $HOME/.config/systemd/usr/default.target.wants, I placed a bunch of services for my desktop session.
Further investigation indicates that the problem lies in the privoxy.service file.This file, included in the latest version of the package fails: [Unit]
Description=Privoxy Web Proxy With Advanced Filtering Capabilities
After=network.target
[Service]
Type=forking
PIDFile=/run/privoxy.pid
ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config
[Install]
W
So I wrote a golang app which I want initialized by systemd whenever my server gets a reboot.
Here's the service file:-
[Unit]
Description=golang wiki initialization
[Service]
Type=forking
PIDFile=/tmp/gowiki.pid-3030
User=root
Group=root
WorkingDirectory=/var/www
ExecStart=/bin/bash -c 'daemonize -o stdout.log -e stderr.log /var/www/wiki'
[Install]
WantedBy=multi-user.target
It appears to w
If there are those who share my dilemna, I have found a not elegant hack which will keep sasc-ng alive until it truly is initiated by systemd itself. This works with both the open-sasc-ng and open-sasc-dkms AUR packages.1) If on a new intall, install latest version of initscripts. It's no longer installed by default2) Create a rc-local.service file and put it in /etc/systemd/system.