On Tue, 13 Oct 1998 21:41:37 +0200 (MEST), you wrote:
> One thing I found out while doing this though, is that diald likes to make
> its own fifo file. I first thought that I would have to create the file
> myself, so I issued a 'touch /var/run/diald.fifo'. But with this file
> already present and not created by diald, I kept getting errors when
> starting diald. I removed the file diald.fifo, restarted diald, and now
> my disconnects (at least) are running smoothly.
Sean,
This is not really the case. If you read the diald man pages you will
notice that the author advises that YOU create the fifo, so that the
access permissions will be set correctly. Diald will create one but
only if one is not first found.
The problem you have run in to is that the command 'touch
/var/run/diald.fifo' does not create a named pipe - it creates a plain
vanilla file. You want the raspberry ripple version:
mkfifo /var/run/diald.fifo
and then set permissions accordingly.
HTH
--
(o_ Ben Williams _o)
//\ [EMAIL PROTECTED] /\\
V_/_ [EMAIL PROTECTED] _\_V
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
