faxgetty & mgetty

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

Hi,

Lorenzo M. Catucci wrote:
> 
> As you can see, mgetty runs well even when spawned by faxgetty... a gret
> result, in my opinion. Now I'm getting mad to get the callback working,
> 
> Here is what I read in the logs:
> 
> 05/18 16:34:34 detaching from ctty...
> 05/18 16:34:39 lock not made: lock file exists
> 05/18 16:34:39 ttyS2: locked
> 05/18 16:35:09 can't read mgetty pid file /etc/mg-pid.ttyS2: No such file or directory
> 05/18 16:35:09 no mgetty on ttyS2, can't use this line
> 05/18 16:35:09 can't get dialout device, exiting: No such file or directory

If mgetty isn't respawned from "init", mgetty's callback scheme won't work
(which is based on "callback dials out, and then signals a running mgetty
to take over").

There are a couple of other callback packages out there, maybe one of them
will work.

> In as much as I can interpret these messages, the problem is with mgetty
> not being respawned from init; 

Yes.

> does there exist some way to have callback
> spawn its own mgetty, to have it work?

No.

gert
-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.