On Wed, 26 Sep 2007 14:22:17 -0400 Charlie Seaman <[EMAIL PROTECTED]> wrote:
> Based on James Knott's info on Linux it would seem that this type of > issue should not occur on Linux. If it did it seems that it might be > one of the *RARE* occurrences that might need a reboot. But, what would > need to be done before you took that route on Linux? OO appears to create an "in-use" flag in /tmp Therefore, if that flag is not deleted when OO is closed, the next instance will think it's already running and refuse to start. For example, here is an OO flag on my computer: /tmp/OSL_PIPE_500_SingleOfficeIPC_f45996626496b1cda1213dac254548d It goes away when I close OO. Accordingly, the best solution is to simply delete that flag from /tmp and all should be well. Rebooting the computer will clear all of the files in /tmp so that is also a solution that will work, but it's a bit more drastic than is actually required. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
