Welcome to the Linux Foundation Forum!
Anyone Know Howto Create a KeepAlive Script?
Xipher_Zero
Posts: 48
in Ubuntu
I run Gnome-Do's Docky interface on a number of systems and occasionally it can crash. I am looking for a way to write a keep alive script that will monitor gnome-do and if it crashes restart it.
Thanks
0
Comments
-
There are several way of fulfilling your requirement. First, your script can make use of pidof to check the pid of the command you wish to monitor. If the pid is empty, there is a possibility of the process is dead, so you run the software again.
Now, the problem is that the software is running on an X environment and the process is owned by the currently logged user. So, when you run the software again, you need to know what user privilege you are going to run the software and the display environment.
I hope my answer could give some enlightenment.
Regards,
Joko0 -
Xipher_Zero wrote:I run Gnome-Do's Docky interface on a number of systems and occasionally it can crash. I am looking for a way to write a keep alive script that will monitor gnome-do and if it crashes restart it.
Thanks
I typically use a perl wrapper (i.e., daemon) for this sort of thing. The perl script starts up, detaches from the terminal, then loops indefinitely, waking up at some interval i specify to run my generic command. In your case, i might ps/pidof |grep Do Docky and relaunch it, if not running. If you're interested, i can dig up a skel of the perl daemon. the same thing can be done in bash, too, if that's more your thang.0 -
also see this thread
http://www.linux.com/component/fireboard/?func=view&id=16&catid=190 -
atreyu wrote:Xipher_Zero wrote:I run Gnome-Do's Docky interface on a number of systems and occasionally it can crash. I am looking for a way to write a keep alive script that will monitor gnome-do and if it crashes restart it.
Thanks
I typically use a perl wrapper (i.e., daemon) for this sort of thing. The perl script starts up, detaches from the terminal, then loops indefinitely, waking up at some interval i specify to run my generic command. In your case, i might ps/pidof |grep Do Docky and relaunch it, if not running. If you're interested, i can dig up a skel of the perl daemon. the same thing can be done in bash, too, if that's more your thang.
Thank you! I'd really appreciate it, I am not a programmer and a skel to start from would be a great help!0 -
Thank you I will check it out!0
-
Here's the basics.
0. this is a Perl script, you have been warned
1. cut and paste this into a file called "mydaemon.pl", then edit...
2. define your sleep interval at the top of the script (my $sleepInt = ...)
3. the program it looks for is "foo.sh". substitute w/your process name.
4. it prints everything to STDOUT. you probably don't want this. ideally, they should go to a log, or be suppressed.
5. test before you run with:perl -cw mydaemon.pl
6. let me know if you need help tweaking...#!/usr/bin/perl use strict; use warnings; use POSIX qw(setsid); use Fcntl ':flock'; use FindBin qw($Script); # define sleep interval here (in seconds) my $sleepInt = 3; # make output line-buffered $| = 1; # daemonize open(SELFLOCK, "<$0") or die "couldn't open $0: $!\n"; flock(SELFLOCK, LOCK_EX | LOCK_NB) or die "another $Script is already running\n"; chdir('/') or die "can't chdir to '/': $!\n"; umask 0; defined(my $pid = fork) || die "can't fork: $!\n"; exit if($pid); setsid || die "can't start a new session: $!\n"; # eternal loop while ( 1 ) { # do thing here... # eg look for pid of 'foo.sh' chomp(my $pid = `/sbin/pidof -x foo.sh`); if($pid){ print "foo.sh (pid $pid) is running\n"; }else{ print "foo.sh is stopped\n"; print "starting foo.sh..."; # start the command system("foo.sh &"); } print "sleeping $sleepInt seconds...\n"; sleep $sleepInt; } # you should never get here exit(1);
0 -
atreyu wrote:Here's the basics.
0. this is a Perl script, you have been warned
1. cut and paste this into a file called "mydaemon.pl", then edit...
2. define your sleep interval at the top of the script (my $sleepInt = ...)
3. the program it looks for is "foo.sh". substitute w/your process name.
4. it prints everything to STDOUT. you probably don't want this. ideally, they should go to a log, or be suppressed.
5. test before you run with:perl -cw mydaemon.pl
6. let me know if you need help tweaking...#!/usr/bin/perl use strict; use warnings; use POSIX qw(setsid); use Fcntl ':flock'; use FindBin qw($Script); # define sleep interval here (in seconds) my $sleepInt = 3; # make output line-buffered $| = 1; # daemonize open(SELFLOCK, "<$0") or die "couldn't open $0: $!\n"; flock(SELFLOCK, LOCK_EX | LOCK_NB) or die "another $Script is already running\n"; chdir('/') or die "can't chdir to '/': $!\n"; umask 0; defined(my $pid = fork) || die "can't fork: $!\n"; exit if($pid); setsid || die "can't start a new session: $!\n"; # eternal loop while ( 1 ) { # do thing here... # eg look for pid of 'foo.sh' chomp(my $pid = `/sbin/pidof -x foo.sh`); if($pid){ print "foo.sh (pid $pid) is running\n"; }else{ print "foo.sh is stopped\n"; print "starting foo.sh..."; # start the command system("foo.sh &"); } print "sleeping $sleepInt seconds...\n"; sleep $sleepInt; } # you should never get here exit(1);
Thanks! I will work on it when I get home and let you know how it goes!0
Categories
- 8.9K All Categories
- 13 LFX Mentorship
- 66 LFX Mentorship: Linux Kernel
- 363 Linux Foundation Boot Camps
- 230 Cloud Engineer Boot Camp
- 70 Advanced Cloud Engineer Boot Camp
- 25 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 845 Training Courses
- 15 LFC110 Class Forum
- 16 LFD102 Class Forum
- 102 LFD103 Class Forum
- 3 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 19 LFD254 Class Forum
- 431 LFD259 Class Forum
- 85 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 16 LFS200 Class Forum
- 692 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 26 LFS241 Class Forum
- 27 LFS242 Class Forum
- 19 LFS243 Class Forum
- 6 LFS244 Class Forum
- 9 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 107 LFS253 Class Forum
- 789 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 51 LFS260 Class Forum
- 78 LFS261 Class Forum
- 13 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 9 LFS268 Class Forum
- 6 LFS269 Class Forum
- 180 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 187 LFW211 Class Forum
- 103 LFW212 Class Forum
- 878 Hardware
- 207 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 723 Linux Distributions
- 81 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 126 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 447 Linux System Administration
- 33 Cloud Computing
- 64 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 747 Programming and Development
- 240 Kernel Development
- 473 Software Development
- 902 Software
- 247 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 314 Installation
- 20 All In Program
- 20 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)