At 10:36 AM 4/19/2004, you wrote: >Barry Buchbinder Sun, 18 Apr 2004 18:56:47 -0400 >>>>> How about the following? >>>>> $ cmd /c start /wait program_being_waited_for > >Tom Roche Sunday, April 18, 2004 8:01 PM >>>> I've never run windows' shell from bash, but that does the job. > >Larry Hall 04/18/2004 07:12 PM >>> [For 'wait n',] 'n' is a proc id. See 'man bash'. > >arrgghh: I tried "{info, man} wait". > >Buchbinder, Barry 04/19/2004 10:03:00 AM: >> (at least on XP) if you just start the program without using >> cygstart or putting it in the background with &, the shell just >> waits for it to finish. > >I'm not sure if the problem is that > >* I'm on 2k > >* the program being run is java-based > >but bash does not stop.
Clearly, whatever your program is, it effectively runs a separate process, otherwise you wouldn't see the problem you do (as Barry points out). It's not strictly related to the O/S or the programming language. I think we've covered this rather off-topic subject well enough. I'd like to suggest that we end the thread here unless something Cygwin-specific surfaces. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/