Hi,
i have a problem with turning a job into backgrund.
When i enter this at the shell:
spice -b darlington.cir -r output.raw > screenout.tmp &
and then let me show the currently running jobs, i get the following output:
+ Suspended (tty output) spice -b darlington.cir -r output.raw >... (4 Replies)
Hi there,
I'm quite new to UNIX for programming. I have a script that does this:
Shows on screen real-time results taken from phone calls and logs them in a file.
However, when I start my script, I want my script to start logging in the file in the background, so I can continue working on... (1 Reply)
i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help.
$cat run_job.ksh
#!/usr/bin/ksh
####################################
typeset -u SCHEMA_NAME=$1
... (1 Reply)
Reposting, as it got lost during the database backup. :(
Via a shell script a spawn 3 background jobs namely a, b & c.
These will take different times to complete.
I want to print a different message on completion of each.
How can i find out when each one has completed independently.
... (19 Replies)
Admins,
We have a strange problem on our solaris zones. We have four zones on a Global server (Sun-Fire-V890; Solaris 10 Update 6) and the SSH sessions to all four zones are terminated at a specific time (11:10 PM) every night. The SSH session to the global server is not terminated.
Also, any... (1 Reply)
Hello,
I am trying to find a way to send several sequential commands via SSH to a remote box in a single command.
Thoughts so far:
1) Can I put them into a function and call the function within the ssh command?
e.g.
ssh <targetserver> $(functionx)
No - then it calls the function in... (4 Replies)
I have a question.
I will be running a background process using nohup and & command at end. I want to send output to a file say myprocess.out.
So will this command work?
nohup myprocess.ksh > myprocess.out &
Thanks in advance guys !!!
:) (3 Replies)
Discussion started by: vx04
3 Replies
LEARN ABOUT HPUX
nohup
nohup(1) General Commands Manual nohup(1)NAME
nohup - run a command immune to hangups
SYNOPSIS
command [arguments]
DESCRIPTION
executes command with hangups and quits ignored. If output is not redirected by the user, both standard output and standard error are sent
to If is not writable in the current directory, output is redirected to otherwise, fails. If a file is created, the file's permission bits
will be set to
If output from is redirected to a terminal, or is not redirected at all, the output is sent to
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari-
able. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of
If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See
environ(5).
International Code Set Support
Single- and multi-byte character code sets are supported.
EXAMPLES
It is frequently desirable to apply to pipelines or lists of commands. This can be done only by placing pipelines and command lists in a
single file, called a shell script. To run the script using
features apply to the entire contents of file. If the shell script file is to be executed often, the need to type can be eliminated by
setting execute permission on file. The script can also be run in the background with interrupts ignored (see sh(1)):
file typically contains normal keyboard command sequences that one would want to continue running in case the terminal disconnects, such
as:
WARNINGS
Be careful to place punctuation properly. For example, in the command form:
applies only to command1. To correct the problem, use the command form:
Be careful of where standard error is redirected. The following command may put error messages on tape, making it unreadable:
whereas
puts the error messages into file
EXIT STATUS
The following exit values are returned:
The command specified by
command was found but could not be invoked
An error occurred in the nohup utility or the specified
command could not be found
Otherwise, the exit status of nohup will be that of the command specified.
SEE ALSO chmod(1), nice(1), sh(1), signal(5).
STANDARDS CONFORMANCE nohup(1)