Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have time 2 time a need for tracking/monitor supervise application that will keep a track on my running scripts. 2 be more precise, i have a python script that i will like 2 run for like 24/7 under any circumstances. After some investigation i found daemontool, but i do think there is a better tools more , lets say, integrated into linux world like for example corn or at.
Hello u all,
I have time 2 time a need for tracking/monitor supervise application that will keep a track on my running scripts. 2 be more precise, i have a python script that i will like 2 run for like 24/7 under any circumstances. After some investigation i found daemontool, but i do think there is a better tools more , lets say, integrated into linux world like for example corn or at.
Spell your words out. And it's "cron", not "corn".
Daemontool appears to be a Windows program...if you're talking about something else, please post a link to the site. The obvious answer (since you wrote the script), is to build some sort of process checker into it, so if the program dies, it will attempt a restart/alert you/take whatever action you want.
I know, correction as been notified...
Anyway, daemontools is definitively a linux tool check out http://cr.yp.to/daemontools.html made by D. J. Bernstein.
More like apache, sendmail and other, create a main process(monitor process) and use working thread.
I know, correction as been notified...
Anyway, daemontools is definitively a linux tool check out http://cr.yp.to/daemontools.html made by D. J. Bernstein.
Ahh...well, if it's already written for Linux/Unix...what other 'integration' do you need???
Quote:
More like apache, sendmail and other, create a main process(monitor process) and use working thread.
Yes..they usually save a PID identifier somewhere, perhaps in /tmp, with the process ID number of the started daemon. You can do the same with your program, and have a part of your script just watch for that PID. If it's seen, wait and check again in some time. If it's not, attempt a restart, and put in whatever restart logic you want. Personally, I try to restart 3 times, and email an administrator if that happens, and stop trying if you can't get things going in three tries.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.