There are a number of possible solotions to this problem:
1. There might be a way to tell MARC to stay as a foregound process.
Most programs that by default puts themselves as a background process
has a command-line option to stay as a foreground process.
2. If you have control of where the output is sent, then you can use a
named pipe to let MARC write the output directly to your program.
3. It may be the case that MARC is not completely detatching itself from
the calling process. Maybe it leaves open files open. If this is true
then you can use a unnamed pipe to detect when the program finishes.
(see popen and/or pipe)
---
Henrik Nordstr�m
Bernd Antweiler wrote:
> The problem: MARC takes itself to the background, system (...)
> returns and my programm wants to continue with working. Error,
> no file available naturally (MARC needs in this case 30 secs.).
