not running in the back ground

Ethros · 03-31-2021, 04:59 PM

I have two lots of programs i need to run in the background but when i close the terminal they close down.

Can anyone help with this

First one is as follows

cd nomp
nvm use 5.10
npm install -g nohup
nohup node init.js

second one is as follows

cd explorer
nvm use 12.14.0
npm install -g nohup
nohup npm start

frankbell · 03-31-2021, 07:41 PM

Try starting them with a trailing ampersand:

Code:

someprogram &

You still will not be able to close the terminal, but the terminal will return the command prompt and you use if for other functions.

scasey · 03-31-2021, 07:49 PM

I’ve always used nohup when starting a job that needed to continue after I logged off. See the man page.

Ethros · 03-31-2021, 07:51 PM

Quote:

Originally Posted by scasey

I’ve always used nohup when starting a job that needed to continue after I logged off. See the man page.

I did but when I closed the terminal it's stops

Emerson · 03-31-2021, 07:54 PM

Try using full path to nohup, like

Code:

/usr/bin/nohup myprogram

Ethros · 03-31-2021, 07:57 PM

Quote:

Originally Posted by Emerson

Try using full path to nohup, like

Code:

/usr/bin/nohup myprogram

these are the paths i use

nohup npm start &

nohup node init.js &

And when i close the terminal they still close the program

Emerson · 03-31-2021, 08:02 PM

I see. You are not listening. Can't fix that.

Ethros · 03-31-2021, 08:03 PM

Quote:

Originally Posted by Emerson

I see. You are not listening. Can't fix that.

we all have to learn somewhere and im very new to this. So maybe a little help is all im asking for

Emerson · 03-31-2021, 08:08 PM

Your shell may have nohup as internal command, and that's what you were using. To make sure you are using the real nohup tool you need to use full path.

Ethros · 03-31-2021, 08:14 PM

Quote:

Originally Posted by Emerson

Your shell may have nohup as internal command, and that's what you were using. To make sure you are using the real nohup tool you need to use full path.

this is why im new to this,

is it like home/ubuntu/explorer?

Emerson · 03-31-2021, 08:19 PM

First you locate nohup

Code:

~ $ whereis nohup
nohup: /usr/bin/nohup /usr/share/man/man1p/nohup.1p.bz2 /usr/share/man/man1/nohup.1.bz2

In my computer it is in /usr/bin/, it is likely you have it in the same location. Then execute it using full path as shown in my earlier post. You need to run CLI commands from console or in a terminal window if you have GUI running.

Ethros · 03-31-2021, 08:26 PM

Quote:

Originally Posted by Emerson

First you locate nohup

Code:

~ $ whereis nohup
nohup: /usr/bin/nohup /usr/share/man/man1p/nohup.1p.bz2 /usr/share/man/man1/nohup.1.bz2

In my computer it is in /usr/bin/, it is likely you have it in the same location. Then execute it using full path as shown in my earlier post. You need to run CLI commands from console or in a terminal window if you have GUI running.

/usr/bin/nohup /usr/share/man/man1/nohup.1.gz
mine is same can you help me with what the full path would be please

/usr/bin/nohup node init.js &

?

computersavvy · 03-31-2021, 08:38 PM

Just that.
The & takes it out of the foreground screen so you can do other things.
The nohup prevents closing the process when you close the screen.

crts · 03-31-2021, 09:04 PM

Alternatively, you might also want to try screen. You can detach from a session, close the terminal and reattach later, again.
Example:

Code:

screen -d -m program # start 'program' in detached mode

You can now close the terminal if you want. You can reattach later with:

Code:

screen -d -r # reattach to session that runs 'program'

You can detach from within a session by pressing C-a + d. If you are running more than one screen session you can use

Code:

screen -ls # list PIDs of all current screen sessions

Then you can attach to one of the sessions by

Code:

screen -d -r [PID] # reattach to session that has PID