how about 'forking' the app into the background??

app&

Never tried this myself as I usuall just leave the ssh session open.
I am doing an RDP to a P3 windows machine to run a 'pic' application that has
no Linux version 'yet'.

try using "screen"
create a screen session before run a command
then just detach the screen before logout
when you re-login, just re-attach the screen you've created. then you
can stop the process or do something else. log out ( not detach the
screen ) when you're finished.

That sounds pretty much like the goal. Here's where my
newbiness is exposed: I can't figure out how to do that.
mp3blaster is interactive and grabs control of the console,
so I'd have to bring up a second console screen on the local
machine. This is easy enough but I don't know what commands
to issue.


> app&
>
>Never tried this myself as I usuall just leave the ssh session open.

That does work, and eliminates the whole problem; but I
want to be able to shut down the local pc... and - it has
become a Project.

Have you tried the 'forking' and shutdown your local computer to see if the
program continues to run?

If this needs to run all of the time would it be better to start this program
via a cron job when the machine boots. I know this can be done as I have a
Linux machine (not Ubuntu) that does this without a login and without kb,
mouse, monitor.
This should be a command added to your runlevel section in like rc.local,
don't have my Ubuntu running at this time (switch OS's).