Les wrote:
On Tue, 2007-05-15 at 21:27 -0500, Les Mikesell wrote:
Arch Willingham wrote:
I tried that. After I did it, when you dbl click on the file, you see a screen flash by very quickly and then it disappears. I looked at the running processes and rdesktop is not running a running process (I'm from the Windows world and what I just typed may be barking up the wrong tree...I just took a SWAG and assumed if it was running t=in the background I would still see rdesktop running but Linux may not work that way).
The problem is that you are in the same process group and get killed by
a signal when your parent shell exits. 'nohup' takes care of an
assortment of things that need to keep working. Try
nohup command &
exit
The 'nohup' redirects output to a file and starts a new process group,
the '&' lets the shell continue instead of waiting, and the 'exit'
should close the shell window.
Thanks, Les,
I Know that old age is supposed to consume gray matter, but come
on.... I couldn't remember the command to save my life.
The usual use of nohup is to start a long-running program from the
command line so you can log out and come back later to find the output
logged to the nohup.out file. These days I usually do everything from a
freenx/NX login and leave windows with long-running programs open or
minimized so when I reconnect I can just pop that window back up.
You can also get the same effect with the vnc module that lets you
access the X console screen remotely but freenx doesn't need as much
bandwidth.
--
Les Mikesell
lesmikesell@xxxxxxxxx
