From: Roland G. <RGi...@cp...> - 2002-08-29 15:03:07
|
Quoting Anders Wallgren <And...@ac...>: > I've tried using nohup (from bash), but it doesn't fix the problem. > From what I've been able to find, this problem only exists on Solaris. OK, I took a look at some nohup source code and indeed it only fixes SIGHUP, but not the problem with job control. Sorry for the false lead. > I found a good description of the problem at > http://archive.develooper.com/per...@pe.../msg61417.html > <http://archive.develooper.com/per...@pe.../msg61417.html> ... > IRIX64 6.5 : /dev/ttyq8 is a tty > SunOS 5.6 : /dev/pts/11 is no tty > Linux 2.2 (Redhat 7.0): /dev/pts/1 is a tty > AIX 4.3 : /dev/pts/3 is a tty I don't think this is the real reason. What this list shows is that the _master_ part of the pty might not be a tty, which is annoying (you have to set tty parameters via the slave fd) but no bug by itself. There might be a coincident that only Solaris shows this behaviour, but Solaris is different in many other ways too. The problem with background execution has to do with the controlling terminal and process groups, I'm sure about that. But I have no idea how to solve it within the realms of IO-Tty or Expect. [BTW, the latest IO-Tty and Expect versions do take into account that the master pty may not be a tty; also IO::Stty is now optional, so that bug report is obsolete.] Hope this clarifies somewhat. Roland -- RGi...@cp... |