To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96102
                 Issue #|96102
                 Summary|unopkg.com dies before unopkg.bin
               Component|framework
                 Version|OOo 3.0
                Platform|All
                     URL|
              OS/Version|Windows, all
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|jl
             Reported by|jl





------- Additional comments from [EMAIL PROTECTED] Tue Nov 11 15:01:58 +0000 
2008 -------
unopkg.com starts unopkg.bin. It terminates either if all pipes to unopkg.bin
are closed or or if unopkg.bin has terminated. The first  creates a problem when
running unopkg.com quickly after each other in a batch. Even if the script waits
for unopkg.com to finish before it starts the next unopkg.com, the next
unopkg.com may fail because unopkg.bin is still alive. That is, the next
unopkg.bin will find the lock file  of the already existing unopkg.bin and then
terminate. 

The fix is to terminate unopkg.bin only if
unopkg.bin has terminated
AND
all pipes are closed.

The latter is important, otherwise the pipes may still contain characters which
have not been written to the console yet. 

See desktop/win32/source/guistdio/guistdio.inc, WaitForMultipleObjects

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to