On Monday, May 25, 2015 at 11:11:34 PM UTC+2, Ron Poulin wrote: > > Mario, > I agree. The solution to this would be an external monitoring process and > an internal responder. I looked at process-watcher / monitor that look > promising as concepts. > > See: https://github.com/yahoo/process-watcher >
uups, I think, I did misunderstand your OP a little bit. ... You want to auto-restart a failed server. Since you were proposing a file watcher, I was thinking in the wrong direction. We have several requests in other threads, that want to restart the server, if someone changed / added a tiddler by hand. .. So my responses my be "strange" for you. So yes a process watcher may be the right tool for your OP. The only problem is, that "how do you know, that the server failed"? The tw app can hang, but the process may be still alive. imo there is no hartbeat at the moment. -mario -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8ea07c48-8d92-4bc4-9100-d8625e5f4186%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
