linux - When to use upstart for Tomcat vs. Tomcat's Daemon Mode? -
according tomcat docs, tomcat can set - on linux/unix - run daemon. however, behave daemon, special configuration required beyond defaults tomcat ships with.
my understanding of true *nix daemon is background, non-interactive program, owned init
process. typically, daemons scheduled background work , never driven input actual user.
here root of question: seems tomcat can given daemon-like behavior it's own daemon mode (first link above) or via number of built-in linux tools (upstart
, init.d
, systemd
, etc.). means have 4 possible scenarios here:
on 1 hand, may choose use tomcat's daemon mode or not. may choose use built-in linux tool or not.
what i'm looking this: what use cases necessitate each of 4 scenarios depicted above? is:
- when use tomcat's daemon mode, and use, say,
upstart
? - when not use tomcat's daemon mode, use
upstart
? - when use tomcat's daemon mode, not use
upstart
? - when use neither?
obviously, in questions, can replace upstart
other tool (systemd
, etc.).
Comments
Post a Comment