Telnet jobs stop after exit

[Boogje]

There may be a very straightforward answer to this question, but I can't seem to find it.
I want to open a telnet/ssh session to the PCH, start a job (e.g. copy some directories, unpack a .rar-file, etc.) and then exit the telnet, while the pch keeps fulfilling my requested job.
The problem is, once I exit the telnet, the jobs disappear. This way I have to keep my pc running just to keep the PCH doing my job.

Is there a solution for this?

[lordy]

It is because
1 the command is a child of the telnet shell.
2. the command is still linked to your telnet io streams

You can get around this in a number of ways:

1. I think the Utils have the linux 'screen' app.

2. You can also type (including brackets)...

Code:

( your_command </dev/null >/dev/null 2>&1 & )

This works most of the time.

3. If you install oversight there is a binary called daemon in the bin/nmt100/ folder.

Code:

/share/Apps/oversight/bin/nmt100/daemon your_command

( or get it from http://oversight.googlecode.com/svn/trun...100/daemon )

[Boogje]

(07-14-2010 02:42 PM)lordy Wrote:  It is because
1 the command is a child of the telnet shell.
2. the command is still linked to your telnet io streams

You can get around this in a number of ways:

1. I think the Utils have the linux 'screen' app.

2. You can also type (including brackets)...

Code:

( your_command </dev/null >/dev/null 2>&1 & )

This works most of the time.

3. If you install oversight there is a binary called daemon in the bin/nmt100/ folder.

Code:

/share/Apps/oversight/bin/nmt100/daemon your_command

( or get it from http://oversight.googlecode.com/svn/trun...100/daemon )

Thanks.
1. screen doesn't seem to be on the list for utils. Would be nice if it were.
2. Since I don't have a clue what you're doing there and it's a lot of hassle to type this every time (let alone memorize it), i'll skip it
3. works like a charm! I downloaded the seperate file and put it in the /bin with winscp+dropbear. Then chmoded it and it works as intended.
You're a lifesaver! No more comments from the wife for leaving the pc running 'for nothing' :-)

[xor]

"nohup your_command"
should work also

[lordy]

Doh. Keep forgetting that one. - worked on too many systems where its not installed when I needed it , so I got used to
option 2 in my list

[Boogje]

[noob alert :-)] is there a way to monitor what the job is doing? (a la screen)
Can you send the output that normally goes to the telnet session somewhere else where you can dynamically follow it up?
Alternatively, can you put it in a text file?

another question: I put that daemon file in /bin, which worked nicely, but upon rebooting the pch it was gone. Is there a way to put it there permanently, or put the path where it is in memory or something?

[lordy]

Try nohup as suggested by xor. as this should be built into the busybox you are using. Output goes to nohup.out (oddly no default output file on C200 busybox version)

Syntax is

Code:

nohup command &

Note with nohup you must add & at the end to run in background.

If using my daemon program output goes to /share/tmp/daemon.out

You can also use standard shell commands to send output where you want.

eg.

Code:

nohup command > log.txt 2>&1 &

daemon command > log.txt 2>&1

The last bit (2>&1) is to put errors in the same file.