Mark,
I did have the fifo line in my diald.conf, but somehow the fifo had been
created as a regular file, rather than a fifo. I deleted
/etc/diald/diald.ctl and fired up diald again and it seems to have sorted
it out.
Anyway, Thanks for your time
Regards
Neale.
On Thu, 11 May 2000 17:35:10 -0400, Mark Frey said:
> Hi Neale!
>
> This is a FAQ. Due to some bug in the code that forks the chat
> process,
> the modem file descriptor inadvertantly gets closed before chat is
> exec'ed. Chat gives the 'Can't get terminal attributes' error because
> it's not got a handle to the modem. Add a fifo statement to your
> diald.conf and the extra open file descriptor should eliminate the
> problem for you. I'm guessing that you did have a fifo in your old
> diald.conf and it's not in the new one you made.
>
>
> Regards,
> Mark.
>
>
>
> Neale Swinnerton wrote:
> >
> > Hi,
> >
> > I'm having problems getting diald to work properly at the moment. I
> have
> > sucessfully had it running in the past, but I inadvertantly deleted
> the
> > diald.conf file and can't get it working since.
> >
> > I have updated to a 2.3.99-pre6 kernel in the mean time which may
> have
> > some bearing. I had no trouble with 2.3.99-pre3 kernels. I have also
> > updated to ppp-2.4.0b2, since it is supposedly required for pre6 and
> > later kernels.
> >
> > I using Redhat6.2.
> >
> > Anyway...problem description
> >
> > I can successfully start a PPP link manually using..
> >
> > # ifup ppp0
> >
> > diald itself starts ok and it seems to install the ethertap
> interface
> > OK....
> >
> > # ifconfig -p
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:3904 Metric:1
> > RX packets:279 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:279 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> >
> > tap0 Link encap:Ethernet HWaddr FE:FD:00:00:00:00
> > inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.255
> > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > Interrupt:5
> >
> > but when I try to initiate a connection I get the following
> appearing in
> > syslog.....
> >
> > May 11 13:58:00 shankly diald[2882]: Trigger: udp
> 192.168.1.1/1063
> > 195.8.69.9/53
> > May 11 13:58:00 shankly diald[2882]: Calling site 192.168.1.2
> > May 11 13:58:01 shankly connect: Initializing Modem
> > May 11 13:58:01 shankly chat[2892]: Can't get terminal parameters:
> > Invalid argument
> > May 11 13:58:01 shankly connect: Failed to initialize modem
> >
> > for the connect argument in /etc/diald.conf I've got the following
> >
> > connect '/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0'
> >
> > Any thoughts? I'm guessing that it's some stupid error on my part,
> but I
> > can't see it.
> >
> > Neale Swinnerton
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> linux-diald" in
> > the body of a message to [EMAIL PROTECTED]
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
