Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.


Help with writing Shell Script to automate process using multiple commands

Login or Register to Reply

 
Thread Tools Search this Thread
# 8  
Hi Sayed,

sorry, but I have almost no knowledge about zabbix beside the fact that I read some news articles about it here and then. Zabbix is a good open source monitoring solution with fine documentation, that'll help you a lot.

Regarding questioning: In this forum there is a monitoring section as well. Another good place is ...

... the Zabbix-Forum:
ZABBIX Forums
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Automate multiple commands
gecko1
Hi, I am trying to count the number of times a string of letters occurs in a file for multiple unique strings of letters. Right now I can do this one at a time using the following code (in this example I am searching for the string "AAA"): echo AAA >> outfile.txt grep -c "AAA" -r...... Shell Programming and Scripting
4
Shell Programming and Scripting
Need help in creating a shell script to automate svnstats process
d8011
Hi, I am trying to create a shell script to automate the following process of getting svn stats:- Step1:- cd to checkout location. Note that the checked code have multiple modules in respective folders Step2:- Execute this command inside each module:- svn log -v --xml >...... Shell Programming and Scripting
0
Shell Programming and Scripting
Writing a loop to process multiple input files by a shell script
evelibertine
I have multiple input files that I want to manipulate using a shell script. The files are called 250.1 through 250.1000 but I only want the script to manipulate 250.300 through 250.1000. Before I was using the following script to manipulate the text files: for i in 250.*; do || awk...... UNIX for Dummies Questions & Answers
4
UNIX for Dummies Questions & Answers
writing a shell script of commands
rahul_11d
Can anyone help me out in visualizing on what is the logic behind simple unix commands. For Eg: ls command lists files and directories, how it displays I need to know the source code for commands like this.... Shell Programming and Scripting
1
Shell Programming and Scripting
Automate Script using pkgrm/pkgadd commands
Insight
This is my first post so hello to all of you! I have a script in bash-3.00 that needs to execute the following: pkgrm (to remove an existing package) pkgadd -d ( to install a new package) The problem is that both commands prompt me to answer either y,n or q in order to proceed with...... UNIX for Advanced & Expert Users
13
UNIX for Advanced & Expert Users
Shell(3pm)						 Perl Programmers Reference Guide						Shell(3pm)

NAME
Shell - run shell commands transparently within perl
SYNOPSIS
use Shell qw(cat ps cp); $passwd = cat('</etc/passwd'); @pslines = ps('-ww'), cp("/etc/passwd", "/tmp/passwd"); # object oriented my $sh = Shell->new; print $sh->ls('-l');
DESCRIPTION
Caveats This package is included as a show case, illustrating a few Perl features. It shouldn't be used for production programs. Although it does provide a simple interface for obtaining the standard output of arbitrary commands, there may be better ways of achieving what you need. Running shell commands while obtaining standard output can be done with the "qx/STRING/" operator, or by calling "open" with a filename expression that ends with "|", giving you the option to process one line at a time. If you don't need to process standard output at all, you might use "system" (in preference of doing a print with the collected standard output). Since Shell.pm and all of the aforementioned techniques use your system's shell to call some local command, none of them is portable across different systems. Note, however, that there are several built in functions and library packages providing portable implementations of functions operating on files, such as: "glob", "link" and "unlink", "mkdir" and "rmdir", "rename", "File::Compare", "File::Copy", "File::Find" etc. Using Shell.pm while importing "foo" creates a subroutine "foo" in the namespace of the importing package. Calling "foo" with arguments "arg1", "arg2",... results in a shell command "foo arg1 arg2...", where the function name and the arguments are joined with a blank. (See the subsection on Escaping magic characters.) Since the result is essentially a command line to be passed to the shell, your notion of arguments to the Perl function is not necessarily identical to what the shell treats as a command line token, to be passed as an individual argument to the program. Furthermore, note that this implies that "foo" is callable by file name only, which frequently depends on the setting of the program's environment. Creating a Shell object gives you the opportunity to call any command in the usual OO notation without requiring you to announce it in the "use Shell" statement. Don't assume any additional semantics being associated with a Shell object: in no way is it similar to a shell process with its environment or current working directory or any other setting. Escaping Magic Characters It is, in general, impossible to take care of quoting the shell's magic characters. For some obscure reason, however, Shell.pm quotes apostrophes ("'") and backslashes ("") on UNIX, and spaces and quotes (""") on Windows. Configuration If you set $Shell::capture_stderr to 1, the module will attempt to capture the standard error output of the process as well. This is done by adding "2>&1" to the command line, so don't try this on a system not supporting this redirection. Setting $Shell::capture_stderr to -1 will send standard error to the bit bucket (i.e., the equivalent of adding "2>/dev/null" to the command line). The same caveat regarding redirection applies. If you set $Shell::raw to true no quoting whatsoever is done.
BUGS
Quoting should be off by default. It isn't possible to call shell built in commands, but it can be done by using a workaround, e.g. shell( '-c', 'set' ). Capturing standard error does not work on some systems (e.g. VMS).
AUTHOR
Date: Thu, 22 Sep 94 16:18:16 -0700 Message-Id: <9409222318.AA17072@scalpel.netlabs.com> To: perl5-porters@isu.edu From: Larry Wall <lwall@scalpel.netlabs.com> Subject: a new module I just wrote Here's one that'll whack your mind a little out. #!/usr/bin/perl use Shell; $foo = echo("howdy", "<funny>", "world"); print $foo; $passwd = cat("</etc/passwd"); print $passwd; sub ps; print ps -ww; cp("/etc/passwd", "/etc/passwd.orig"); That's maybe too gonzo. It actually exports an AUTOLOAD to the current package (and uncovered a bug in Beta 3, by the way). Maybe the usual usage should be use Shell qw(echo cat ps cp); Larry Wall Changes by Jenda@Krynicky.cz and Dave Cottle <d.cottle@csc.canterbury.ac.nz>. Changes for OO syntax and bug fixes by Casey West <casey@geeknest.com>. $Shell::raw and pod rewrite by Wolfgang Laun. Rewritten to use closures rather than "eval "string"" by Adriano Ferreira. perl v5.12.5 2012-11-03 Shell(3pm)

Featured Tech Videos