[arch-general] In the systemd scheme, where should startup/stop scripts for things systemd can't handle go?

[David Benfell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

So now that I've got a network through systemd, I ran into trouble
with some daemon service files that I crafted by hand.

None of the following directives will work (culled from different files):

ExecStartPre=cd /etc/solr
ExecStart=$JAVA_HOME/bin/java -jar $JAVA_OPTS start.jar $JETTY_OPTS >>
/var/log/jetty.log 2>&1
ExecStop=kill `pidof -o %PPID /usr/sbin/dictd` 2>/dev/null 1>/dev/null

Basically lots of things that would be normal in a shell are
problematic. So I need to create separate scripts to start and stop
some daemons. I'm thinking I definitely do not want to use /etc/rc.d
for this (I had to back out and go back to init and /etc/rc.d is still
in use for that).

Is there some consensus on where such scripts should go?
- -- 
David Benfell
benfell at parts-unknown.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQEv+RAAoJELT202JKF+xp9rAP/1+hg9rapqIp8xI01vJ6Uvyd
twIXA5bD3LvGS36FkCTmapdpcNKxGzCgxIoXcST0Qe1uJsrFboTl7LGJ14dmBBqg
05tqpvg6Vv4/tv+ac4S6dIO9uY0SmyzZoQMue5B0cvGvEAb7vcdh+dCjru0/YGis
8Nzsyyv3c/hJE43GIL4buz46cqKhcJqQyJAs8xXBbM50uchr2vpOQ6F2COMs196C
4NeLnPut4Gc5xZJd0cJmS/cqAYd7CYH0UX6gGYfxo9GT+CVoLJmnSeooNiRZZBAN
uO/Fq7azsN8jRBWynmS0Ckqt5Dx1ErPyW/J2uj3UinMbg2XeOK2cLbmYAsmWyLIu
9fnWfsllHXEs+phbk4qUerojHDH4p/IQAyNV2FsiLVQmAV0FXKZB39NaM+7ws7z4
X9xbRcWKM8kTAflmPdiaGGmDJ7v8E0yhaB/0IbTbAhM2HDQxUVvgpHZFSyiQbR8T
pED90wLp2iv10Jl16K/GRdn6GjMLS4QVftAWdPUyfR9NlLV/wPGVsB4jVmTmLzM5
jw0JJvKyrybZvJP0l/G/mUX+0KxHHcSQaldhTL2q5jlD+ZbHOda1inwgH5Dq+eJ2
ruJDNXYIy0Jy7fa1J3Wh+9FRk9LEo9VEdoQhPzjjhYXZ4qnkwRd5etmUun99v6/2
FX8jWC4EAX6Gb0gq9Fxh
=zGji
-----END PGP SIGNATURE-----