| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
Somebody somewhere told me how to do SPAWN from inside a command procedure without hassle. I forget where and I forget how. It's something like specifying /INPUT=NL:, but I'm not sure. According to the documentation, SPAWNing from inside a command pro- cedure is not supported. But it does work. How do I do it? #6 <_Jym_>\
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 111.1 | JAWS::KAISER | Thu Apr 18 1985 08:41 | 3 | ||
That's right; /INPUT=NL:. ---Pete | |||||
| 111.2 | LATOUR::AMARTIN | Fri Apr 19 1985 22:44 | 9 | ||
Not just from a command procedure. I have found /IN:NL: to be vital when using SPAWN interactively. If I want to have, say, a CONVERT/SHARE running in the background to copy a file over the network while I am doing something useful, then I have to specify /INPUT:NL:. Otherwise, a ^Y to stop a program in the foregorund will also halt the CONVERT. Is this true, or am I mistaken about something? /AHM/THX | |||||
| 111.3 | SCOTTY::MPALMER | Mon Apr 22 1985 12:11 | 3 | ||
yes, I've noticed that too - and if it's not a bug it's certainly annoying - OOB ASTs vectored to children processes! especially since the child gives no termination notice. | |||||
| 111.4 | WEBSTR::BEYER | Wed Apr 24 1985 12:53 | 4 | ||
It's documented, therefore not a bug. I don't think I could find the reference in the manuals now, though. HRB | |||||