I would be happy to run it in screen but I don't understand what the
advantage is. I can redirect the output to a log, without using screen, and
I can automate restarts with something like Puppet or Supervisor. What do I
need screen for?
On Tuesday, October 23, 2012 7:37:03 AM UTC-4,
If you run your process in screen/tmux it will be attached to active
TTY, it will not receive HUP signal.
Also if there would be important (any?) output from process you will see
it in tmux/screen.
So either nohup it or run it in session that doesn't terminate after you
exit.
HTH,
Hubert.
This is a very ignorant question on my part, but if I use screen to capture
the output, then isn't the output being held in memory? I guess I don't
know much about how the server manages terminal memory. I suppose if the
terminal is set to only keep 10,000 lines (which I think is true on my
(into {} (filter #(- % val is-current?)
map-of-all-user-maps)
I tested this and it works. I admit it is a bit of magic Clojure-fu
wizardry that is a bit over my head. I am again impressed with how concise
Clojure can be.
On Monday, October 22, 2012 3:09:39 PM
For our long-running clojure server app, I found that adding `:jvm-opts
[-server]` to the project.clj increased performance a bit. It's too much
info for this post, but hers'a good description from
SO:
Not sure if that is a case but could your run your software in some long
running shell like tmux or screen.
You redirected all standard file descriptors, so it should not be a
problem, but it is worth a try.
HTH,
Hubert.
AtKaaZ wrote:
You could save the std out and err to some .log and can
I am fairly new to Clojure, and new to the JVM, so I do not know how to
diagnose a dying app.
I have a very simple app that tries to keep track (in memory) of who is
logged in. I'll show the code below. I compiled this app and uploaded it to
my server and launched it like this:
On Mon, Oct 22, 2012 at 2:30 PM, larry google groups
lawrencecloj...@gmail.com wrote:
And the core.clj looks like this:
(ns who-is-logged-in.core
(:gen-class)
(:import (java.util Date))
(:require clojure.string clojure.java.io who-is-logged-in.memory_display
On Mon, Oct 22, 2012 at 2:51 PM, Aaron Cohen aa...@assonance.org wrote:
I think that what you are doing here is something like the following?:
(into {} (keep #(is-current? %2) map-of-all-user-maps)
Bah, used the wrong function, since keep works on nil/not-nil this should be:
(into {} (filter
On Mon, Oct 22, 2012 at 2:54 PM, Aaron Cohen aa...@assonance.org wrote:
On Mon, Oct 22, 2012 at 2:51 PM, Aaron Cohen aa...@assonance.org wrote:
I think that what you are doing here is something like the following?:
(into {} (keep #(is-current? %2) map-of-all-user-maps)
Bah, used the wrong
2012/10/22 larry google groups lawrencecloj...@gmail.com
I have not yet added any security to the app, so there is a chance that
someone is shutting it down with spam. (I just got this app up last week,
and was planning to add security checks this week).
I do not know much about programming
Thank you much for your help. My Clojure code is clumsy, for sure. Your
version of much better.
The server is Jetty.
There are only 2 routes in the whole app, at the 2 URLs I posted above.
I will start logging OutOfMemory errors.
If memory is not the problem, what other problems should I
Well, here is the beginning of some primitive logging. I set up the app on
one server and then, on a different server, I started calling this URL and
logging the results:
http://www.tailormadeanswers.com:4/show-resources
The cron script was only calling once every 5 minutes, so maybe it
You could save the std out and err to some .log and can inspect it later,
I'd expect you'd see some exceptions if any were thrown.
who-is-logged-in-1.0.1-standalone.jar 4 /dev/null stdouterr.log
On Tue, Oct 23, 2012 at 12:12 AM, Michael Klishin
michael.s.klis...@gmail.com wrote:
14 matches
Mail list logo
