no subject (file transmission)

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

root wrote:
> From: Russell Nelson <nelson@crynwr.com>
> To: mgetty@muc.de
> Subject: Problem with call_program
> 
> I defined R_CALL_PROGRAM in voclib.h, which causes the voice mode code
> to execute vg_call.  Problem is that the shell script expects to be
> able to use stdin/stdout to talk to the tty, but the process that owns
> the lock file is now gone.  So it gives up soon after answering.

Why should the process owning the lock file be gone??

I just took a look into the code: vgetty is calling the "R_CALL_PROGRAM"
via exec(), so it will get the same PID as the vgetty process that spawned
it. So, though it's not the same process as before (btw, same happens with
/bin/login!), there is still a process with the PID that's in the lock
file, the lock file is valid, noone will remove it.

I'd assume that your R_CALL_PROGRAM somehow calls the ``zplay'' program
with the wrong arguments (missing `-S'? Klaus?) and zplay removes the lock
file. Could you send me (or better, Klaus) your R_CALL_PROGRAM for
checking for such errors?

gert
-- 
Ok, Ihr habt gewonnen, hier ist eine neue signature...

Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-3243328                         gert.doering@physik.tu-muenchen.de