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
- All Categories
- 178 LFX Mentorship
- 178 LFX Mentorship: Linux Kernel
- 772 Linux Foundation IT Professional Programs
- 382 Cloud Engineer IT Professional Program
- 175 Advanced Cloud Engineer IT Professional Program
- 75 DevOps IT Professional Program - Discontinued
- 7 DevOps & GitOps IT Professional Program
- 102 Cloud Native Developer IT Professional Program
- 7.6K Training Courses & Learning Paths
- 9 AI & ML Training
- 1 Blockchain & Decentralized Identity Training
- 28 Cloud & Containers Training
- 3 Cybersecurity Training
- 2 DevOps & Site-Reliability Training
- 1 Linux Kernel Development Training
- 2 Networking Training
- 2 Open Source Best Practice Training
- 5 System Administration Training
- 1 System Engineering Training
- 4 Web & Application Development Training
- 797 Hardware
- 202 Drivers
- 68 I/O Devices
- 37 Monitors
- 96 Multimedia
- 173 Networking
- 91 Printers & Scanners
- 91 Storage
- 771 Linux Distributions
- 81 Debian
- 68 Fedora
- 23 Linux Mint
- 13 Mageia
- 24 openSUSE
- 151 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 469 Linux System Administration
- 31 Cloud Computing
- 73 Command Line/Scripting
- Github systems admin projects
- 101 Linux Security
- 79 Network Management
- 101 System Management
- 46 Web Management
- 146 Mobile Computing
- 20 Android
- 111 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 403 Off Topic
- 126 Introductions
- 33 Study Material
- 1K Programming and Development
- 310 Kernel Development
- 716 Software Development
- 1K Software
- 416 Applications
- 182 Command Line
- 5 Compiling/Installing
- 71 Games
- 320 Installation
- Archived
- 183 Small Talk
- 2 LFD140 Class Forum
- 1.4K LFS258 Class 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)