Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers

Webmaster Forum / ColdFusion / Server Administration / September 2004



Tip: Looking for answers? Try searching our database.

cfmx6.1 updater breaking sandboxing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
disco stew - 07 Sep 2004 04:55 GMT
Hi everyone, we have recently installed the cfmx6.1 updater on one of our
servers and found, after trying to do some cf sandboxing and things didn't
work, that the cfmx6.1 updater had changed most of the files in
/opt/coldfusionmx/runtime/bin to be owned by root! These files are normally
owned by the user that cf runs as (eg nobody). Changing the files back to be
owned by user nobody stoppped cf complaining about sandboxing. Has anyone else
experience this? Are MM aware of this? We are running CFMX6.1 on Solaris 8 with
Apache 2.0.50.

Thanks in advance.
thewolf - 21 Sep 2004 10:04 GMT
Hi,
I just applied the ColdFusion MX 6.1 Updater 1 to a CF Server Installation
running on RH Enterprise Linux 3 and sandboxing seems to work just fine.

I also noticed that the files in that directory have updated permissions, but
that doesn't seem to affect the sandbox functionality.

What problems are you noticing?

Ciao.
disco stew - 23 Sep 2004 02:28 GMT
When  trying to add a sandbox, cf gave me a permissions error. This was after i
installed the updater. I have since installed the updater on another Solaris 8
box and again, same error  with the files in /opt/coldfusionmx/runtime/bin now
owned by root.  The files in /opt/coldfusionmx/runtime/bin are normally owned
by 'nobody', as is the case on our other  cf servers.
thewolf - 23 Sep 2004 09:24 GMT
Hi,
you are right, I tried to add a new sandbox and I got the following error
message:
* Unable to apply security updates:
[]coldfusion.server.ServiceException: /opt/coldfusionmx/runtime/bin/jvm.config
(Permission denied)
So I changed the permissions on the jvm.config file (chmod apache:root
jvm.config) and tried again: it worked fine.
Did you try that?

I am going to report Macromedia this bug, hopefully they will release an
hotfix for it.

Ciao.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.