John H. Robinson, IV([EMAIL PROTECTED])@Fri, Jun 08, 2007 at 11:32:50AM -0700: > Karl Cunningham wrote: > > I had a job running in an ssh console that I didn't want to restart, but > > I had to log off the machine. So I ctrl-z'ed it, figuring I'd deal with > > it later. > > > > I'm logged back in again and I can see it's still running with ps. Is > > there a way to regain control of the job by its pid, or some other way? > > Not now - the console it was associated with is gone. > In the future, you can start it under screen (if you set your $SHELL to > screen, this makes it almost automatic) > > You can still send signals (SGHUP, SIGTERM, SIGCONT, SIGQUIT) but you > are not going to get the STDIN, STDOUT, or STDERR of the command to > redrect to your terminal. > > -john >
If you don't have screen (or don't want to install it, nohup <command> & will re-parent the pid under init. The output will go to nohup.out for subsequent perusal. Screen is more fun and versatile, though. :-) Plus, if you really want to reconnect STDOUT to your terminal output, nohup won't do that. I've been working in mixed environments lately, and this is the first time I've really had any difficulty with screen. Mostly, it's the keymappings that give me heartburn. I'm not a term[cap,info] or terminal expert, so I'm sure that's part of it. However, I always have some irritating issue going from putty|ReflectionX to RHEL4(xterm or gnome-term) to a ksh on Solaris8 or HPUX. I do wish it could split horizontally, too. :-) (or vertically, depending your perspective -- I want side-by-side windows). In fact I'm -->||<-- this close to switching to ratpoison window manager, or something similar. Wade Curry syntaxman -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
