Get KDE program to run permanently.

xtothat · 09-19-2008, 06:44 AM

Hi everyone, new member here.

I am trying to make a program run more reliably by making it restart if it closes (through crash or pressing the close button).

I have tried using BASH "while true" loops but haven't really had any success.

If anybody can think of any way this could be done. Preferably BASH or something in xinit, but I could use python or perl if necessary.

I'm using KDE 3.5 (if that makes a difference)

Anyway... If anybody can help at all I would be most grateful.

Thanks to any and everybody in advance!

X-T

willysr · 09-19-2008, 09:27 AM

try monit. Hope it suit your needs

xtothat · 09-19-2008, 09:57 AM

Awesome! Looks like just what I need! Thanks for your speedy reply, your help is much, much appreciated!

X-T

David the H. · 09-19-2008, 10:15 AM

Just for the record, why doesn't the while loop work for you? I've used it before myself with unstable programs, such as once when there was a bug in ktorrent that made it crash occasionally on my system. In that case I only had to do one other thing to make it work, and that was run it with the --nofork and --nocrashhandler options to keep it from launching as a background process and popping up the crash report dialog every time.

xtothat · 09-22-2008, 08:52 AM

Hi guys... Thanks for all your support... I've actually fixed my while loop. I was being an idiot and forgetting where I needed to put semicolons. Also a less pretty, but smaller (by a whole line of code

) way of doing it would be to do this:

Code:

#!/bin/bash
/path/to/program
/path/to/this/script

Anyway... Thanks again for everybody's help, and I hope that my membership will continue to be as enjoyable as this!

X-T

i92guboj · 09-22-2008, 08:59 AM

Quote:

Originally Posted by xtothat

Hi guys... Thanks for all your support... I've actually fixed my while loop. I was being an idiot and forgetting where I needed to put semicolons. Also a less pretty, but smaller (by a whole line of code

) way of doing it would be to do this:

Code:

#!/bin/bash
/path/to/program
/path/to/this/script

Anyway... Thanks again for everybody's help, and I hope that my membership will continue to be as enjoyable as this!

X-T

The bad thing about this alternate way is that bash instances will pile up. Each time you call the script a new bash session is opened, and they will live forever, filling your ram.

That's not a problem if it crashes a couple of time, but it's a big problem if it happens a few dozen times. So, I'd use the while loop instead.

xtothat · 09-22-2008, 09:19 AM

I'm learning something new every post. I'll go with the while loop. Thanks!!!

piete · 09-22-2008, 10:06 AM

Code:

#!/bin/bash
/path/to/program
exec /path/to/this/script

Should keep the number of instances down to exactly one, since instead of spawning a new instance, it'll just reuse the same one (or more accurately, replace whatever spawned it) ...

I hope

i92guboj · 09-23-2008, 05:20 AM

Quote:

Originally Posted by piete

Code:

#!/bin/bash
/path/to/program
exec /path/to/this/script

Should keep the number of instances down to exactly one, since instead of spawning a new instance, it'll just reuse the same one (or more accurately, replace whatever spawned it) ...

I hope

Yes, that's correct as well.

xtothat · 09-26-2008, 12:56 PM

Cool! Thanks!