I like it when someone says 'do not do this' without some supporting cost/benefit rationale.
My next question is why not ? I'll add my own salt here: - Daemonizing does not alter business logic, it can be kept separate using more than one entry point - Supervisory functions are not as generic as some may think. You may have a need to support extra stuff in daemon mode that may/may not be offered by your platform supervisor - Portability might be an issue which is easier to deal with within the JVM than having to cope with different platform specific supervisors As to the why not, I am eager to see them. In general your mileage will vary depending on your needs. This is the real answer to many of the 'do not do this' so named 'rules'. Luc P. Sent from my iPhone > On May 29, 2015, at 08:02, piastkra...@gmail.com wrote: > > Stuart, about the JSVC, I am curious if you have an opinion about the > argument made in the comments of this blog post: > > "Great post, but in reality you should never write app that daemonize them > self. Always use supervisors that your system provides." > > http://www.rkn.io/2014/02/06/clojure-cookbook-daemons/ > > > > > >> On Wednesday, May 27, 2015 at 3:53:24 AM UTC-4, Stuart Sierra wrote: >> JSVC (Apache Commons daemon for Unix) is excellent for this sort of thing. >> There's a Windows Services version too. >> –S >> >> >>> On Tuesday, May 26, 2015 at 12:38:30 PM UTC+1, Colin Yates wrote: >>> Hi, >>> >>> I am venturing into new territory using http-kit, as I usually use a >>> 'managed' web server container like tomcat and have a few questions about >>> packing and running a JAR file: >>> >>> - are there are convenient service wrappers for windows and/or Linux >>> - any best practice around managing class path for things like logback.xml >>> >>> I have a jar created from lein uberjar and java -jar the.jar works, but >>> this seems a long way away from automated deployment :). >>> >>> Any advice welcome - thanks! > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
