Igor:
So...three quick questions:
1. How long does it typically take for the OS to delet the
mutex on its own? I would think it's just a few seconds.
2. Is there anything we can do to accelerate this?
3. Can we have Kaboodle simply wait until the mutex clears
before it tries to restart VNC?
One quick bug report:
4. When I set a display/port for the VNC server, after I
enable the checkbox, the default value 0/5900 is restored
the next time I open the PropertyPanel.
-Scott
On Mon, 6 May 2002, Igor Kotelevsky wrote:
> Hello Scott.
> You can find that Kaboodle restarts VNC server too slowly.
> Here is explanation this.
>
> When WinVNC server startup, it creates a named mutex
> and checks to see whether that mutex already existed in the system.
> (Name of this mutex is "WinVNC_Win32_Instance_Mutex".)
> If it failed to create the mutex, then there is a previous instance of
> WinVNC running,
> which must be requested to quit cleanly.
> I have found that WinVNC server creates above mutex at startup, but not
> deletes it at finishing.
> OS automatically deletes above mutex, but this occurs in a certain time
> after WinVNC termination.
>
> So Kaboodle must expect when OS will execute this.
> If Kaboodle will not do this, that WinVNC server is not started and user
> will see
> MessageBox("Another instance of WinVNC is already running").
>
> - Igor
>
>
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
