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 server), then I would never have to worry about more than 10,000 lines being held in memory, which is not too much trouble. Or I could run this inside of a shell inside of emacs inside of shell (which I often do) and then rely on emacs to be sure that the shell doesn't use up the server's memory?
Actually, this is a good idea. I'll do this. On Wednesday, October 24, 2012 2:11:19 PM UTC-4, Hubert Iwaniuk wrote: > > 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. > > larry google groups wrote: > > > 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, Hubert Iwaniuk wrote: >> >> 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 inspect it later, >> I'd expect you'd see some exceptions if any were thrown. >> who-is-logged-in-1.0.1-standalone.jar 40000 </dev/null >stdouterr.log & >> >> On Tue, Oct 23, 2012 at 12:12 AM, Michael Klishin >> <michael....@gmail.com>wrote: >> >>> 2012/10/23 larry google groups <lawrenc...@gmail.com> >>> >>>> If memory is not the problem, what other problems should I look for? >>> >>> >>> Unhandled exceptions, although in the case of a Web app, Jetty and >>> similar should cover last >>> resort exception handling that will prevent main JVM thread from >>> terminating. >>> >>> -- >>> MK >>> >>> http://github.com/michaelklishin >>> http://twitter.com/michaelklishin >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clo...@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+u...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> >> >> >> >> -- >> I may be wrong or incomplete. >> Please express any corrections / additions, >> they are encouraged and appreciated. >> At least one entity is bound to be transformed if you do ;) >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@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+u...@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 post to this group, send email to clo...@googlegroups.com <javascript:> > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+u...@googlegroups.com <javascript:> > 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 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
