Gaal Yahas wrote:
>
> On Mon, Dec 20, 1999 at 11:47:14PM +0200, Nimrod Mesika wrote:
> >
> > nimrodm:~$ cat /etc/ppp/ip-up.local
> What happens when licq isn't running and reading the pipe?
> Unless I'm mistaken, your ip-*.local scripts would block, which
> is probably not what you want.
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?)
> Also, what does putting the data on a pipe get you? The process
> would still have to poll the pipe, wouldn't it?
Not quite. The process will block on read() and will not use the cpu
until data is available. Licq is a threaded app, so blocking one thread
will leave the others running.
-- Nimrod.
=================================================================
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]
