11-14-2012
A background script can't read from the terminal. Maybe if you opened it again, read count < /dev/tty or something like that... But then, why bother putting it in the background if the first thing it's going to do is block?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: Prateek007
3 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: prabhutkl
2 Replies
3. UNIX for Advanced & Expert Users
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)
Discussion started by: shahnazurs
3 Replies
4. Shell Programming and Scripting
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)
Discussion started by: rohithji
2 Replies
5. Shell Programming and Scripting
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)
Discussion started by: maitree
3 Replies
6. Shell Programming and Scripting
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)
Discussion started by: gd05
2 Replies
7. Shell Programming and Scripting
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)
Discussion started by: asavaliya
8 Replies
8. Shell Programming and Scripting
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)
Discussion started by: ketanraut
9 Replies
9. Shell Programming and Scripting
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
$HOME/myScript/test/background_sh
When I view my script in background with psu commend
> psu | grep background_sh
I see following output
UID PID PPID C ... (1 Reply)
Discussion started by: vaibhav
1 Replies
10. Shell Programming and Scripting
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
PTY(4) BSD Kernel Interfaces Manual PTY(4)
NAME
pty -- BSD-style compatibility pseudo-terminal driver
SYNOPSIS
device pty
DESCRIPTION
The pty driver provides support for the traditional BSD naming scheme that was used for accessing pseudo-terminals. When the device
/dev/ptyXX is being opened, a new terminal shall be created with the pts(4) driver. A device node for this terminal shall be created, which
has the name /dev/ttyXX.
New code should not try to allocate pseudo-terminals using this interface. It is only provided for compatibility with older C libraries that
tried to open such devices when posix_openpt(2) was being called.
FILES
The BSD-style compatibility pseudo-terminal driver uses the following device names:
/dev/pty[l-sL-S][0-9a-v] Pseudo-terminal master devices.
/dev/tty[l-sL-S][0-9a-v] Pseudo-terminal slave devices.
DIAGNOSTICS
None.
SEE ALSO
posix_openpt(2), pts(4), tty(4)
HISTORY
A pseudo-terminal driver appeared in 4.2BSD.
BUGS
Unlike previous implementations, the master slave device nodes are destroyed when the PTY becomes unused. A call to stat(2) on a nonexistent
master device will already cause a new master device node to be created. The master device can only be destroyed by opening and closing it.
The pty driver cannot be unloaded, because it cannot determine if it is being used.
BSD
August 20, 2008 BSD