Script termination without pressing Enter key[nohup]
I have a script in which we have used nohup. Once script is executed it will be terminated only when enter key is pressed. I want the script to be terminated without pressing enter key
without pressing the enter key ..manually...
how can we read the enter key ..from the shell script..so that the script termintes automatically.
eg:
telnet a.b.c.d xxxx
now " how to read the enter key" tho terminate the script (1 Reply)
for automating telnet using shell script.....
as we enter alphabetic characters inside shell script...how can we do the same for the enter key......Is there any character for the enter key
so the enter key need not be pressed manually...... (3 Replies)
Hi,
I have a script in which i have to ask user to press the ENTER key to proceed further. can you please help me how can i achive this in my scripting?
echo "All the executables builded Successfully "
echo " Press Enter to Go Back to the Main Menu"
... (2 Replies)
Hey, I'm writing this BASH script, I recently started learning BASH after I did Java and I'm pretty new to the syntax.
Anways, what I want to do is simple, I coudn't find the right information though:
Let's say I make a :
read -p "Press ENTER to go back to menu" choice
.....
What is... (34 Replies)
Hi,
I'm porting an install script from AIX to Red Hat (2.6.18-164.el5 #1 SMP)
I have this script working in both AIX and HP-UX.
The script is a wrapper for a Micro Focus Server Express install program. It responds to the install program questions with a here-now list. Responses includes... (14 Replies)
#Build label and text box
$main->Label(
-text => "Input string below:"
)->pack();
$main->Entry(
-textvariable => \$text456
)->pack();
$main->Button(
-text => "Search",
-command =>
sub {
errchk ($text456)
... (4 Replies)
Discussion started by: popeye
4 Replies
LEARN ABOUT MOJAVE
nohup
NOHUP(1) BSD General Commands Manual NOHUP(1)NAME
nohup -- invoke a utility immune to hangups
SYNOPSIS
nohup [--] utility [arguments]
DESCRIPTION
The nohup utility invokes utility with its arguments and at this time sets the signal SIGHUP to be ignored. If the standard output is a ter-
minal, the standard output is appended to the file nohup.out in the current directory. If standard error is a terminal, it is directed to
the same place as the standard output.
Some shells may provide a builtin nohup command which is similar or identical to this utility. Consult the builtin(1) manual page.
ENVIRONMENT
The following variables are utilized by nohup:
HOME If the output file nohup.out cannot be created in the current directory, the nohup utility uses the directory named by HOME to create
the file.
PATH Used to locate the requested utility if the name contains no '/' characters.
EXIT STATUS
The nohup utility exits with one of the following values:
126 The utility was found, but could not be invoked.
127 The utility could not be found or an error occurred in nohup.
Otherwise, the exit status of nohup will be that of utility.
SEE ALSO builtin(1), csh(1), signal(3)STANDARDS
The nohup utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BUGS
Two or more instances of nohup can append to the same file, which makes for a confusing output.
BSD July 19, 2001 BSD