03-25-2011
I think you can run your first process in background by putting & at the end of the command and then run rm command.
This User Gave Thanks to pravin27 For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Basically, I would like to run an mpirun query on my web server to query your databases via yours when using the BLAST program, however the server seems not able to execute even basic mpirun programs such as cpi (to calculate pi). Are there any settings I should take note of?
I am running Perl... (0 Replies)
Discussion started by: tesswulf
0 Replies
2. Shell Programming and Scripting
Hi,
please can someone point me in the right direction with a shell scripting problem.
I want to execute a command in a for loop and the command should be started not one-by-one meaning the for loop is waiting for the exit code , it should be started in parallel.
I have a plain text file... (3 Replies)
Discussion started by: networkfre@k
3 Replies
3. Shell Programming and Scripting
Hi All,
I have 3 shell scripts, Script1,Script2 and Script3. Now I want to run Script1 and Script2 in parallel and Script3 should depend on successful completion of both Script1 and Script2.
Could you please suggest an approach of acheiving this...
Thanks in advance (2 Replies)
Discussion started by: itsme_maverick
2 Replies
4. Red Hat
Hi Folks,
I have a small doubt, the binary commands under /bin and /sbin as well as other path binary files, if you peek deep into that, you can find the difference in the way of normal perl programming and some commands will be like binary files. how are the commands executing like the... (3 Replies)
Discussion started by: gsiva
3 Replies
5. Shell Programming and Scripting
Hi,
I want to run these two commands one after the other.
awk 'BEGIN {OFS="\t"} {print $2}'
sort -u
rather than typing awk 'BEGIN {OFS="\t"} {print $2}' file1 > file2, then sort -u file2 > file3. Is it possible to run both commands on file1 then get output file3?
Its kinda hard for... (5 Replies)
Discussion started by: kylle345
5 Replies
6. Shell Programming and Scripting
I need to execute a command to run my script several times with varying parameters
perl ex.pl -b 130198 -e 130884 -c plot plot.txt 1_plot.txt
perl ex.pl -b 1345 -e 1308 -c plot plot.txt 2_plot.txt
perl ex.pl -b 1345567 -e 130898 -c plot plot.txt 3_plot.txt
.
.
.
100's of excutions
... (2 Replies)
Discussion started by: Lucky Ali
2 Replies
7. Shell Programming and Scripting
Hi Experts,
There is a shell script that accepts positional parameter between 1-25 to execute case statement of script depending upon the parameter passed.
Now I need to run all the 25 sessions parallely. In each option of case statement it is connecting with sqlplus and executing a select... (11 Replies)
Discussion started by: Opamps123
11 Replies
8. Shell Programming and Scripting
I have n number of SQL queries needs to executed in Shell. Result of this query need to assign in a variable. Once all the queries are executed script needs to exit.
Sample Query:
SQL 1: Select Count(*) from TABLE GROUP BY COL1,COL2
SQL 2: Select Count(*) from TABLE GROUP BY COL1,COL2
... (2 Replies)
Discussion started by: Niranjancse
2 Replies
9. Shell Programming and Scripting
Hi all.
Long time!!
Hope you're doing well..
I've stumbled on a peculiar siutaion here, and would expect help from this forum on a clean resolution.
We are running an rm and find command simultaneously from two different Unix sessions of the same user(let's say USER01) and on the same... (3 Replies)
Discussion started by: kumarjt
3 Replies
10. UNIX for Beginners Questions & Answers
Hi Folks,
I have requirement to pull a bunch of SQL's from a table in DB and execute them in parallel and update the status of each query as and when they complete. Can you please help me with ideas on how this can be achieved?
create table list_of_sql
(
id number,
full_sql... (3 Replies)
Discussion started by: member2014
3 Replies
LEARN ABOUT OPENDARWIN
bgerror
bgerror(n) Tcl Built-In Commands bgerror(n)
__________________________________________________________________________________________________________________________________________________
NAME
bgerror - Command invoked to process background errors
SYNOPSIS
bgerror message
_________________________________________________________________
DESCRIPTION
The bgerror command doesn't exist as built-in part of Tcl. Instead, individual applications or users can define a bgerror command (e.g. as
a Tcl procedure) if they wish to handle background errors.
A background error is one that occurs in an event handler or some other command that didn't originate with the application. For example,
if an error occurs while executing a command specified with the after command, then it is a background error. For a non-background error,
the error can simply be returned up through nested Tcl command evaluations until it reaches the top-level code in the application; then the
application can report the error in whatever way it wishes. When a background error occurs, the unwinding ends in the Tcl library and
there is no obvious way for Tcl to report the error.
When Tcl detects a background error, it saves information about the error and invokes the bgerror command later as an idle event handler.
Before invoking bgerror, Tcl restores the errorInfo and errorCode variables to their values at the time the error occurred, then it invokes
bgerror with the error message as its only argument. Tcl assumes that the application has implemented the bgerror command, and that the
command will report the error in a way that makes sense for the application. Tcl will ignore any result returned by the bgerror command as
long as no error is generated.
If another Tcl error occurs within the bgerror command (for example, because no bgerror command has been defined) then Tcl reports the
error itself by writing a message to stderr.
If several background errors accumulate before bgerror is invoked to process them, bgerror will be invoked once for each error, in the
order they occurred. However, if bgerror returns with a break exception, then any remaining errors are skipped without calling bgerror.
Tcl has no default implementation for bgerror. However, in applications using Tk there is a default bgerror procedure which posts a dialog
box containing the error message and offers the user a chance to see a stack trace showing where the error occurred. In addition to allow-
ing the user to view the stack trace, the dialog provides an additional application configurable button which may be used, for example, to
save the stack trace to a file. By default, this is the behavior associated with that button. This behavior can be redefined by setting
the option database values *ErrorDialog.function.text, to specify the caption for the function button, and *ErrorDialog.function.command,
to specify the command to be run. The text of the stack trace is appended to the command when it is evaluated. If either of these options
is set to the empty string, then the additional button will not be displayed in the dialog.
SEE ALSO
after(n), tclvars(n)
KEYWORDS
background error, reporting
Tcl 7.5 bgerror(n)