home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!jamie
- From: jamie@cdevil.unx.sas.com (James Cooper)
- Subject: Re: Problems with cback.o.. 100% background procs
- Originator: jamie@cdevil.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <C0DywK.69n@unx.sas.com>
- Date: Tue, 5 Jan 1993 14:57:56 GMT
- References: <C0CrLq.5uD@usenet.ucs.indiana.edu>
- Nntp-Posting-Host: cdevil.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 20
-
-
- In article <C0CrLq.5uD@usenet.ucs.indiana.edu>, shulick@cineret.ucs.indiana.edu (Sam Hulick) writes:
- >
- >I tried to make a server (using a port, and WaitPort()) with cback.o so
- >all I'd have to type is "testd" instead of using "run <nil: >nil:
- >testd". Well, it does background right away, but if I try to exit the
- >shell, it (the shell) hangs. Why is this?
-
- You have to take care of the _BackgroundIO vector one way or the other (this is
- documented), and you **must** compile with the (v5.10) -Li or (v6.0) NOSTDIO
- option to make sure you don't have a "stderr" open. "stderr" is always just an
- "Open("*",MODE_OLDFILE);", so it will lock the shell.
-
- --
- ---------------
- Jim Cooper
- (jamie@unx.sas.com) bix: jcooper
-
- Any opinions expressed herein are mine (Mine, all mine! Ha, ha, ha!),
- and not necessarily those of my employer.
-