try using something along these lines: 1) go with ssh to a shell on your server.
2) use screen 3) launch your cgi script 4) detach. Your script should stay running... you might need a secondary script or tool to monitor the first one to see if it fails and then relaunch it. On Tue, May 31, 2011 at 12:46 PM, Richard Gaskin <ambassa...@fourthworld.com > wrote: > Shao Sean wrote: > > if you can run revCGI on your web host you can actually use it to run >> servers (the cgi process does not "die") but make sure to check with >> your host that you are within their ToS as they most limit the amount >> of CPU cycles, ram, time, etc... >> > > How do you launch the Rev CGI engine in a way that keeps it alive after > it's done processing the startup handler? > > I've even tried using nohup, and all manner of different scripts, and thus > far have been unable to set up the CGI engine to stay alive, even on my own > custom server in my office. > > -- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > LiveCode Journal blog: http://LiveCodejournal.com/blog.irv > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
