Putting a command in the background means that you lose the flow. Your initial:-
.... will just give you two timestamps almost immediately sequentially and your script will continue whilst the copy make still be progressing.
What are you actually after? If you keep the copy in the foreground of your script (take off the nohup and the &) then you will get the correct before & after times.
For a marker telling you the elapse (and other info) just use this:-
I hope that this helps
Hi all,
I have one script test.sh for which I pass two arguments. In the same script I need to submit this script in background using nohup. My script like this and it is working in HP-UX os but not Solaris.
#! /bin/sh
if
then
MTR_PID=$$
export MTR_PID
echo "test.sh $1 $2... (3 Replies)
Hi everyone -
I'm trying to start a run of LAMMPS (which takes an input file) with mpiexec on multiple processors. I want to combine this with nohup so that I can log off the node. I've used the syntax below successfully on one cluster, but it doesn't work on the new one I'm using. Any... (0 Replies)
Hi,
I'm trying to run database restore script with the nohup command as it will run for long hours since if I run it normally, the putty session will become inactive and the restore gets terminated. The command I use is
nohup db2 -tvf FBR_NODE0000.scr -z FBR_NODE0000.log &
But the problem is... (2 Replies)
when i have a function definition and function call in my script , i am unable to run my script in background with nohup..
Help me out please..... (3 Replies)
Hi,
I am running the below script. When i run the script normally it executes fine but when i run the same script using nohup it throws an error as getStatus.sh: syntax error at line 3: `(' unexpected . Can you let me know why it is so?
while
do
. $(dirname $0)/include.sh
cd... (2 Replies)
why, when i run my shell with sh command it run without problem, but when run with nohup nombreshell.sh $ command not run correctly... values obtained from database are not displayed in the csv file.
My shell do that:
1° data base access with sqlplus:
read_sql_stmt() {
typeset stmt=$1... (3 Replies)
Hi ALL,
Is there any way to pause a running process under nohup ?
I have fired a build commands with required flags under nohup as below. now how can
I pause the started build process.
nohup make DEVICE=ap DEBUG=1 &
I understand we can use ctrl + z to pause a foreground process... (3 Replies)
Hi All,
I am facing issue in running a process in nohup. I ran a process in terminal since it is taking too long to complete I need to make it as background and nohup. I tried below and was able to make it in back ground
1. Cntrl + Z
2. bg
I am using Korn Shell so disown is not working... (5 Replies)
Hi All,
Can anyone please help me understanding what the difference between the below two?
1. script.sh &
2. nohup script.sh & (2 Replies)
Discussion started by: Anupam_Halder
2 Replies
LEARN ABOUT OSX
rake
RAKE(1) Ruby Programmers Reference Guide RAKE(1)NAME
rake -- Ruby Make
SYNOPSIS
rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE] [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE]
[-r MODULE] [--rules] [variable=value] target ...
DESCRIPTION
Rake is a simple ruby(1) build program with capabilities similar to the regular make(1) command.
Rake has the following features:
o Rakefiles (Rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax
to worry about (is that a tab or a space?).
o Users can specify tasks with prerequisites.
o Rake supports rule patterns to synthesize implicit tasks.
o Flexible FileLists that act like arrays but know about manipulating file names and paths.
o A library of prepackaged tasks to make building rakefiles easier.
OPTIONS --version Display the program version.
-C
--classic-namespace
Put Task and FileTask in the top level namespace
-D [PATTERN]
--describe [PATTERN]
Describe the tasks (matching optional PATTERN), then exit.
-E CODE
--execute-continue CODE
Execute some Ruby code, then continue with normal task processing.
-G
--no-system
--nosystem Use standard project Rakefile search paths, ignore system wide rakefiles.
-I LIBDIR
--libdir LIBDIR Include LIBDIR in the search path for required modules.
-N
--no-search
--nosearch Do not search parent directories for the Rakefile.
-P
--prereqs Display the tasks and dependencies, then exit.
-R RAKELIBDIR
--rakelib RAKELIBDIR
--rakelibdir RAKELIBDIR
Auto-import any .rake files in RAKELIBDIR. (default is rakelib )
-T [PATTERN]
--tasks [PATTERN] Display the tasks (matching optional PATTERN) with descriptions, then exit.
-e CODE
--execute CODE Execute some Ruby code and exit.
-f FILE
--rakefile FILE Use FILE as the rakefile.
-h
--help Prints a summary of options.
-g
--system Using system wide (global) rakefiles (usually ~/.rake/*.rake ).
-n
--dry-run Do a dry run without executing actions.
-p CODE
--execute-print CODE
Execute some Ruby code, print the result, then exit.
-q
--quiet Do not log messages to standard output.
-r MODULE
--require MODULE Require MODULE before executing rakefile.
-s
--silent Like --quiet, but also suppresses the 'in directory' announcement.
-t
--trace Turn on invoke/execute tracing, enable full backtrace.
-v
--verbose Log message to standard output (default).
--rules Trace the rules resolution.
SEE ALSO ruby(1)make(1)
http://rake.rubyforge.org/
REPORTING BUGS
Bugs, features requests and other issues can be logged at <http://onestepback.org/redmine/projects/show/rake>.
You will need an account to before you can post issues. Register at <http://onestepback.org/redmine/account/register>. Or you can send an
email to the author.
AUTHOR
Rake is written by Jim Weirich <jim@weirichhouse.org>
UNIX November 7, 2012 UNIX