> When I run dctrl from xterm, dctrl paints, has focus, but does not respond
> to mouse events. /etc/diald/diald.ctl exists and I know dctrl finds it.
I'm running the same version (diald-0.16 with diald-patch-0.16.5) and experienced the
same problem as well. It did not happen all of the time, so I
expected a race condition, specially since I got the following syslog
messages, whenever it failed. But the file was clearly there:
Nov 21 15:56:59 exulaf dialdNov 21 15:56:59 exulaf diald[91]: FIFO: full
monitor connection to monitor /tmp/dctrl.432 requested
Nov 21 15:56:59 exulaf diald[91]: FIFO: could not open pipe /tmp/dctrl.432:
No such device or address
I suspected, that diald tries to open the FIFO before it is created. The dctrl
source clearly indicates otherwise, but nevertheless I could fix the problem by
introducing an "exec sleep 2" right after the creation of the FIFO, before diald is
notified. Works for me, don't know why...
Diffs below.
Maybe someone can explain?
Christoph
----------------------------------------------
*** dctrl Sat Nov 21 15:59:04 1998
--- dctrl.old Sat Nov 21 17:38:35 1998
***************
*** 222,228 ****
set monfifo /tmp/dctrl.[pid]
catch {exec mkfifo -m 0600 $monfifo}
- exec sleep 2
fifoCmd "monitor $monfifo"
set monfd [open $monfifo r]
fileevent $monfd readable {stateChange}
--- 222,227 ----
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
