24 Jul 12, 12:58PM
(24 Jul 12, 02:20AM)ShadowFlameZ Wrote: Cemer did not come here to hear that he should drop the VPS he and whop just purchased yesterday. He was asking how he could solve his problem, not how he could replace it (and possibly encounter even MORE problems).Well, if you ask for help, you might not always hear what you wanted to hear. Point is, the best solution for this kind of problem is to switch to a different host. Having a VPS reboot once a day is simply not acceptable, not if you pay for it. The only time a virtual server should reboot is when it (or the host machine) gets a kernel upgrade/security update (and not even than if you're using ksplice), or when it's migrated.
/rant
That kind of cron hack isn't really the optimal solution, more like a "gets the job done" one. It's okay as a temporary kludge for processes that crash frequently (note temporary - if something crashes all the time, either report a bug or get rid of it). If you just want to make sure something is run whenever the server boots, use an init script.