Shell Programming and Scripting

Hi all,
I am unable interpret this code .........

nohup $OPSSHLPATH/mkt_sas_load_cic.sh $db_name $process_id $loc_mm > $OPSLSTPATH/mkt_sas_load_cic.out &

Thanks ....In advance

nohup keeps a command running even after user logs off, & runs the script in background and > direct the standar output to mkt_sas_load_cic.out

Bye.

nohup keeps a command running even after connection to any server breaks or user logs off and it keeps the script running inbackground, would make the out file as mkt_sas_load_cic.out in your scripts case.

When you people say "will keep the command running" do you mean until completion ? Or does it make it so like an infinitive loop (i.e. the command will run, and after completion, run again and again and again..) ?

It means until completion.

Regards.

Thanks. So, this means that, say I have a script called whatever.sh that takes like 1 hour to complete, I run nohup thescript and it will run the script even if I exit the terminal afterwards ? kind of putting the script in the background with &, right ?

When you exit a session, any processes running are sent a HUP signal. Unless the process is ignoring the signal it will exit upon receipt of SIGHUP. The nohup command is one way of protecting processes from this signal.

That has almost nothing to do with foreground/background processes. A foreground process can read characters from /dev/tty while a background process cannot. You can type your interrupt character, usually Control-c. to send SIGINT to all foreground processes. I don't believe that any nohup command will protect jobs from SIGINT. (A few nonstardard nohup commands exist that protect jobs from SIGTERM or SIGQUIT. This violates the Posix standard.)

HUP stands for hang-up. You used to dial up to Unix systems with a modem. You would disconnect by "hanging-up" the connection.