dialling out with vgetty

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

Wolfram Gloger wrote:

> Yes, but for only about 4 years :-).

That's sounds pretty good. Why had I no success so far...

> > I tried to use the cua* device for diald to call out,
> 
> No, this is definitely not an option.  The cua* devices will
> actually go away completely some time.

Yes, I thought about it, and the FAQ is telling the same.

> Sounds like a locking problem, please make sure that vgetty and
> diald agree on the lockfile directory (probably already the case)

I thought about it, but vgetty really realizes, that diald tries to lock
the device. And there is no problem with starting the connect script, the
logging file shows that diald really starts the connect script. Just that the
connect script can't initialize the modem and dies...

> and that diald writes ASCII logfiles (early versions didn't by
> default, they wrote binary files and erased ASCII ones such as
> the one from vgetty!).

I have a very recent version of diald and vgetty (maybe not the latest versions,
but not an early version either). diald writes ASCII lockfiles and both use the
same directory (at least I'm pretty sure that they do, because vgetty realizes,
if diald uses the lockfile)

So, could there be any other problem?

Thanx again for answering.
Christian
-- 
As far as you can, enjoy every moment of every day.
---ICQ#21196326---http://www.tu-harburg.de/~secw2604/---