> True. It's a bug. KDE fires up licq automatically so I have never
> noticed this bug. Now how do we fix it (without checking for a process
> named 'licq' or anything like that. How do you make sure a fifo has
> someone on the other end?)
OPEN(2) Linux Programmer's Manual OPEN(2)
NAME
open, creat - open and possibly create a file or device
[...]
ERRORS
[...]
ENXIO O_NONBLOCK | O_WRONLY is set, the named file id a FIFO and no
process has the file open for reading.
Or, the file is a device special file and no corresponding
device exists.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
