You don't need to daemonize

Re:You don't need to daemonize by quicksilver03 on Sunday June 28, 2015 @05:40PM (#9795223)

I tend to always use daemonize to start a Java program because typically I need to pass several startup options (like Xms, Xmx, etc.) and systemd unit files cannot perform even the simplest variable interpolation needed [1].

Someday systemd will go beyond simple key-value substitution, and on that day I'll stop using daemonize.

[1]: http://www.opsfordevelopers.com/2015/05/startup-scripts-for-...

[ Parent | on HN ]

Re:You don't need to daemonize by hactually on Sunday June 28, 2015 @07:16PM (#9795523)

What's wrong with doing something like the following:

...

[Service]

Type=forking

EnvironmentFile=-/usr/local/myJavaConfig

ExecStart=/bin/sh -c '${JAVA_HOME} ${JAVA_OPTS}'

Or if you're after passing things in, use the other technique that lets you use systemctl myservice@your_sub.service

[ Parent | on HN ]

Re:You don't need to daemonize by JdeBP on Sunday June 28, 2015 @10:32PM (#9796124)

Two things are wrong, neither of which, however, make daemonize appropriate. First, and trivially, there's a missing /bin/java (-: Second, that's a potential readiness protocol and a main PID mismatch. See http://unix.stackexchange.com/a/200365/5132 for details. And then http://askubuntu.com/a/624871/43344 . Remembering to exec is another lesson to bring along from the daemontools world.

[ Parent | on HN ]

Re:You don't need to daemonize by yrro on Monday June 29, 2015 @04:55AM (#9797033)

That's a case for creating a wrapper shell script that you launch through ExecStart=. Nothing to do with whether your process does the daemon(7) dance or not.

[ Parent | on HN ]

Re:You don't need to daemonize by quicksilver03 on Monday June 29, 2015 @05:10AM (#9797074)

Correct, I should've been clearer that I use daemonize mostly out of frustration with systemd limitations and inability to tell me precisely what's wrong when there are errors launching the service.

[ Parent | on HN ]