News for hackers. Stuff that matters.
Re:Running Lisp in Production by PuercoPop on Friday June 26, 2015 @04:08PM (#9787420)
And in that case how do you handle the monitoring of the system?
Re:Running Lisp in Production by aidenn0 on Saturday June 27, 2015 @12:10AM (#9789069)
This is why I switched from running daemons in tmux to having them start a slime listener; I can monitor them from any standard process monitor that will log errors and restart (I use daemontools with a run-script that sends me an e-mail to notify me of the restart).
Re:Running Lisp in Production by lisper on Friday June 26, 2015 @04:20PM (#9787483)
I don't understand the question. Once it's running, it's like any other server, and you monitor it like you would any other server written in any other language.
Re:Running Lisp in Production by WalterGR on Friday June 26, 2015 @09:27PM (#9788690)
Speculation here, but based on the context, I think the question is: Some daemon-izer solutions will monitor the daemon and e.g. restart it if it's unresponsive. How do you handle this slash how is this handled in the Common Lisp world?
Re:Running Lisp in Production by lisper on Saturday June 27, 2015 @02:11AM (#9789286)
As a last resort, if Lisp becomes totally unresponsive, you kill the process and restart, same as any other language. But it's pretty rare to lose the REPL, so usually you can fix any unexpected problems through that.