| View previous topic :: View next topic |
| Author |
Message |
AHBLawyers
Agent
Joined: Aug 02, 2010
Posts: 15
|
 Posted: Mon Jan 28, 2013 8:00 am Post subject: |
|
Yup worked great, thanks a TON. Question, so why do you have to avoid /var/tmp ? Being a *nix guy did Apple say you shouldn't use /var/tmp?
Just Curious |
|
| Back to top |
|
 |
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 28, 2013 9:35 am Post subject: |
|
Right now, we can still create Unix domain sockets in any writable folder. However, if Mac OS X's application sandboxing is enabled, Mac OS X will only allow Unix domain sockets to be created in the user's Home folder.
Although Apple does not require that we use application sandboxing, Apple started requiring application sandboxing for new submissions to their Mac App Store. Digital signing of applications also started as an App Store-only requirement. Fortunately, we had already implement digital signing before Apple made it a requirement in Mac OS X 10.8 Mountain Lion.
We think it is very likely that, like digital signing, this same requirement may be required for all Mac applications in a future release of Mac OS X so we are trying to handle any likely application sandboxing incompatibilities now instead of waiting until after Apple has actually imposed this requirement.
In general, we try to prepare for any big changes that Apple puts into new Mac OS X releases. In the past, Apple has broadcast planned Mac OS X changes like CoreText, Versions, Full-Screen, and digital signing of applications well before they actually happen so we usually put a high priority on keeping up with Apple's changes. In addition to the Unix domain sockets change, in the last couple of patches we have been upgrading any of our code or NeoOffice's underlying OpenOffice.org code that uses Mac OS X functions that Apple has marked as likely to be removed from future versions of Mac OS X.
Patrick |
|
| Back to top |
|
|
rpin
Blue Pill
Joined: Feb 05, 2013
Posts: 1
|
| Posted: Tue Feb 05, 2013 2:49 am Post subject: |
|
Hi Patrick,
We've had the same issue since 3.3 patch 2 under 10.6 and 10.8 network accounts, and I can confirm the latest test patch works fine under both. We don't do much with extensions, but I have installed one which seems to work as advertised, so I guess this is working too.
Thanks!
Robbert |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Tue Feb 05, 2013 9:35 pm Post subject: |
|
| rpin wrote: | | We've had the same issue since 3.3 patch 2 under 10.6 and 10.8 network accounts, and I can confirm the latest test patch works fine under both. We don't do much with extensions, but I have installed one which seems to work as advertised, so I guess this is working too. |
Thank you for testing the new code. Although we only changed a small number of lines of code, we consider it to be a big change so having confirmation that it works on a range of Mac OS X versions for multiple Mac OS X users with networked home directories makes me feel confident that we this code will allow us to work around the limitations that Unix domain sockets had.
As for extensions, I did some testing and I found that the only time that our new code gets used is when you install or uninstall an extension using the /Applications/NeoOffice.app/Contents/MacOS/unopkg.bin command in a Terminal window. This command is not commonly used but if you do use it, it would be great to hear if you can install and uninstall extensions when running as a user with a mounted Home folder.
Patrick |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Wed Feb 06, 2013 7:46 pm Post subject: |
|
FYI. My last post reminded me that we made some code changes for the "unopkg.bin" Terminal command to work in Mac OS X's application sandbox. Although the changes are not needed yet in NeoOffice 3.3, I put the changes in the following test patch now so that the "unopkg.bin" command is "futureproofed" against future Mac OS X versions as much as possible.
If anyone in this forum topic has uses the "unopkg.bin" command, can you install the following test patch and confirm that you can install and uninstall an extension using the command?:
Intel:
http://juliette.neooffice.org/test/NeoOffice-3.3-Patch-4-Test-7-Intel.dmg
Patrick |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Fri Feb 22, 2013 10:35 am Post subject: |
|
I just wanted to check and see if the latest test patch is working OK or not. We are planning on including the fixes in the next official NeoOffice patch in early March so if you encounter any problems when using the latest test patch, please don't hesitate to let us know.
Patrick |
|
| Back to top |
|
|
AHBLawyers
Agent
Joined: Aug 02, 2010
Posts: 15
|
| Posted: Fri Feb 22, 2013 10:42 am Post subject: |
|
| Working great in our Production environment, I have 8 users using it for 8 hours a day. We don't use any add ons so I never tested the unopkg program. |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Wed Mar 06, 2013 10:18 am Post subject: |
|
FYI. I have included fix for this bug in NeoOffice 3.3 Patch 5. The patch can be downloaded from the NeoOffice patch download page.
Patrick |
|
| Back to top |
|
|
|
