Re: another 1.10 job control bug?

[Chris Herborth <herborth@53iss6.waterloo.ncr.com>]

What you wrote:
> % frob datafile
> ...
> ^Z
> {% bg}
> % logout
> 
> I would expect to get a message indicating that there are stopped 
> {backgrounded} jobs. (probably from the shell being polite)
> 
> If I were to do :
> 
> % frob datafile &
> % logout
> 
> Then I would expect to be able to logout and know that frob is running
> happily without a tty, and not laying claim to mine.
 
On the SysV boxes here, you have to:

bash% nohup frob datafile &
bash% ^D

Otherwise the process is terminated as soon as you log out AND kill your
telnet; telnet from my box stays attached to the SysV box until I kill
it if there are running processes.

Just FYI...  Things don't seem to work they way we'd like 'em, even on
"real" UNIX.

> Bop me one if I'm barking up the wrong tree here, but once the user
> indicates that they're leaving, the tty should be free. If there
> are processes that think that it's still theirs, this is a bug.

I don't know if the tty stays on the SysV box, but as far as my local
machine is concerned, the connection is still valid.

-- 
----------========================_   /\ ============================----------
Chris Herborth                    \`o.0'       herborth@53iss6.Waterloo.NCR.COM
Information Products Developer    =(___)=
AT&T Global Information Solutions    U