how to dissassociate proccess with the shell?

[fusama]

Here's what I want to do. I want to ssh (via putty) into my gentoo box and start some long-running job, say "emerge kde-meta" and then close putty and have the job keep running (until it completes, obviously).

I have found no combination of &, nohup, disown, or disown -h that would do this. (I was using bash if it matters) The best I did was that one combination (sorry, don't remember which one) that would get the job to not die when putty closed, but it stopped executing, which doesn't do me much good. (I was using a second ssh connection (via putty) to watch what was going on when I closed the first ssh session). With all other combinations I tried the process died when putty closed.

It seems like this is something that should be possible, but I'm at a loss as to how to do it.

Thanks.

[timeBandit]

nohup command & does this. The process will block if it needs any input however (e.g., emerge -a would be bad).

Another, far more flexible option: app-misc/screen.
_________________
Plants are pithy, brooks tend to babble--I'm content to lie between them.
Super-short f.g.o checklist: Search first, strip comments, mark solved, help others.

[termite]

emerge screen, then run something like

[beandog]

you don't have to name the session if you want, anyway.

just do screen, then detach it. then screen -r or screen -x to retach it, using the session name if there's more than one.

anyway, like everyone has said ... lots of ways to use screen. ++
_________________
If it ain't broke, tweak it. dvds | blurays | blog | wiki

[Mad Merlin]

[ddriver]

Another way is to run the command using "batch". batch is just an alias for "at now".