I have been looking around and did not find anything that answers this straight up... so, forgive me if I didn't dig enough.
I have everything ready to switch to systemd but I have a couple of daemons that do not have it's equivalent in systemd.
Should I wait until the maintainers update their packages or there is another way I'm missing here?
The daemons are crashplan and supersonic.... If i'ts of any help.
Last edited by Xi0N (2012-10-22 07:10:27)
Create the required service files yourself, submit them upstream.
But they are aur packages.... Should I create the scripts and forward them to the maintainer?
Ideally, upstream, so that they will incude them for all users, not just those who use the AUR. If they're slow to include them, however, you could ask the aur maintainer(s) to do it until upstream gets their act together.
Any kind fella that understands the new systemd way of scripting cares to try to do a startup unit for subsonic / supersonic-git? Both packages from AUR.... I will try myself, but I don't trust my skills that much...
See here, it is super easy. http://0pointer.de/blog/projects/system … ins-3.html
And you have numerous examples to inspire you in /usr/lib/systemd/system.
Ok, this one seems to work:
[Unit] Description=Supersonic Multimedia Server After=network.target [Service] Type=forking #PIDFile=/opt/crashplan/CrashPlanEngine.pid #EnvironmentFile=/opt/crashplan/bin/run.conf WorkingDirectory=/var/supersonic ExecStart=/var/supersonic/supersonic.sh start ExecStop=/var/supersonic/supersonic.sh stop [Install] WantedBy=multi-user.target
Just in case anyone needs it or wants to improve it.... thanks guys!! Now my system is 100% working with systemd+brand new vertex4 ssd FAST AS HELL for being a 5 year old computer.....