02-17-2011
I only guess this code but i am glad you confirmed it.
So is the command "crontab -e " correct ? to enter that code to schedule the script?
After that if i want to make changes to that script how do it do that ?
Thanks for all your help!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi..
i wolud like to know if it´s possible use the crontab command in my script.
the idea is what the script starts automatically, but i don´t know how to do it.
please, help me....
thanks
jonathan (1 Reply)
Discussion started by: DebianJ
1 Replies
2. Shell Programming and Scripting
I know my question maybe eazy, but it realy cause a problem for me
I have a Perl script to run and get some output, I run this script using perl /moutaz/ciscolog/telnet.pl
I made another script as follow:(/moutaz/ciscolog/script)
#!/bin/bash
perl /moutaz/ciscolog/telnet.pl
cp... (6 Replies)
Discussion started by: moutaz1983
6 Replies
3. Solaris
hi,
how can I add a new value to crontab file using a script not using the command " crontab -e " .
ex:
echo " 10 10 * * * " >> /var/spoll/cron/crontabs/<username>
how can I do that in a correct way??
thanks, (3 Replies)
Discussion started by: Ahmed waheed
3 Replies
4. Shell Programming and Scripting
Hi,
How to add a cron job in /etc/crontab using a shell script.??:confused:
Actually the requirement is we need to run a script say, XXX.sh every 10 min through “cron”.
That can be achieved by adding the below code line in the /etc/crontab , (i.e., “crontab -e ” command to add this to the... (4 Replies)
Discussion started by: Dedeepthi
4 Replies
5. Solaris
Hi
I have successfukky created a sh script that runs perfectly well when run. It contains within a pl script that when run through a crontab will not run. Are there restrictions running a pl in cron? (14 Replies)
Discussion started by: rob171171
14 Replies
6. Solaris
hi All, here is the problem: I'm not able to specify a PATH inside the user crontab file (/var/spool/cron/crontabs). The only syntax it accepts is the usual "* * * * * file" I'm not able to add PATH, or HOME, or MAILTO, or anything else. when I try to save the crontab, I have the error: ... (1 Reply)
Discussion started by: joe_x
1 Replies
7. Shell Programming and Scripting
Hi All,
I am running a script to find the CPU and memory utilization of the server. Script name is atul. When i run this script then it gives the desired output as DATE, CPU and MEMORY utilization....as mentioned below:
$
$ cat atul
A=`date| cut -d" " -f1-4; top -d 1 -n 1 | awk '/^CPU... (5 Replies)
Discussion started by: atulbassi83
5 Replies
8. UNIX for Dummies Questions & Answers
Hi guys
Can someone help me with a crontab script please?
I have to sort the files from /bin and put the first 3 of then (with size and path) in /home/user/bin_size
i write the command:
find /bin/ | xargs ls -lS | awk 'FNR<4{print($5, $9)}' > /home/user/bin_size which is working but when I... (2 Replies)
Discussion started by: G30
2 Replies
9. UNIX for Dummies Questions & Answers
Hi guys
Can someone help me with a crontab script please?
I have to sort the files from /bin and put the first 3 of then (with size and path) in /home/user/bin_size
i write the command:
find /bin/ | xargs ls -lS | awk 'FNR<4{print($5, $9)}' > /home/user/bin_size
which is working but when... (6 Replies)
Discussion started by: G30
6 Replies
10. UNIX for Dummies Questions & Answers
I have crontab setup via crontab -e
I was wondering if its possible to create a cron job from a script so when the script is run the cron job is created? (3 Replies)
Discussion started by: scriptnewbie
3 Replies
LEARN ABOUT OPENSOLARIS
catch
catch(1T) Tcl Built-In Commands catch(1T)
__________________________________________________________________________________________________________________________________________________
NAME
catch - Evaluate script and trap exceptional returns
SYNOPSIS
catch script ?varName?
_________________________________________________________________
DESCRIPTION
The catch command may be used to prevent errors from aborting command interpretation. The catch command calls the Tcl interpreter recur-
sively to execute script, and always returns without raising an error, regardless of any errors that might occur while executing script.
If script raises an error, catch will return a non-zero integer value corresponding to the exceptional return code returned by evaluation
of script. Tcl defines the normal return code from script evaluation to be zero(0), or TCL_OK. Tcl also defines four exceptional return
codes: 1 (TCL_ERROR), 2 (TCL_RETURN), 3 (TCL_BREAK), and 4 (TCL_CONTINUE). Errors during evaluation of a script are indicated by a return
code of TCL_ERROR. The other exceptional return codes are returned by the return, break, and continue commands and in other special situa-
tions as documented. Tcl packages can define new commands that return other integer values as return codes as well, and scripts that make
use of the return -code command can also have return codes other than the five defined by Tcl.
If the varName argument is given, then the variable it names is set to the result of the script evaluation. When the return code from the
script is 1 (TCL_ERROR), the value stored in varName is an error message. When the return code from the script is 0 (TCL_OK), the value
stored in resultVarName is the value returned from script.
If script does not raise an error, catch will return 0 (TCL_OK) and set the variable to the value returned from script.
Note that catch catches all exceptions, including those generated by break and continue as well as errors. The only errors that are not
caught are syntax errors found when the script is compiled. This is because the catch command only catches errors during runtime. When
the catch statement is compiled, the script is compiled as well and any syntax errors will generate a Tcl error.
EXAMPLES
The catch command may be used in an if to branch based on the success of a script.
if { [catch {open $someFile w} fid] } {
puts stderr "Could not open $someFile for writing
$fid"
exit 1
}
The catch command will not catch compiled syntax errors. The first time proc foo is called, the body will be compiled and a Tcl error will
be generated.
proc foo {} {
catch {expr {1 +- }}
}
SEE ALSO
break(1T), continue(1T), error(1T), return(1T), tclvars(1T)
KEYWORDS
catch, error
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+--------------------+-----------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+--------------------+-----------------+
|Availability | SUNWTcl |
+--------------------+-----------------+
|Interface Stability | Uncommitted |
+--------------------+-----------------+
NOTES
Source for Tcl is available on http://opensolaris.org.
Tcl 8.0 catch(1T)