[
http://jira.magnolia.info/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257#action_17257
]
Alvaro Arce commented on MAGNOLIA-1959:
---------------------------------------
Well as far as I'm concerned
Adding the startup.sh and the magnolia_control.sh scripts to do firewall, and
then locking and unlocking (several times) the firewall to prevent further
changes does the trick.
Is like if the firewall GUI wouldnt update succesfully the changes into the
firewall, and locking unlocking the scripts kinds of force the update into the
firewall.
At least for me that did the trick.
> Leopard (osx 10.5) issues
> -------------------------
>
> Key: MAGNOLIA-1959
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1959
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.5
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
>
> There seems to have been a couple of reports from people having trouble
> running Magnolia 3.5 rc4 (bundled or with installer) on Leopard.
> Some tracks at the moment:
> - there might be some ports/security settings which are different from
> Tiger(10.4), and Magnolia will not run from the /Applications directory,
> while it will run perfectly from a user's home directory. (no errors on
> startup, everything seems to be fine, but one can't access localhost:8080)
> - there might be some "max.files opened" issues, with settings which are
> different from Tiger(10.4).
> When you encounter such issue, please try to tail /var/log/system.log while
> starting up, it might have interesting hints.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
