[ http://jira.jboss.com/jira/browse/JBAS-1224?page=history ]
Scott M Stark resolved JBAS-1224:
---------------------------------
Resolution: Done
This is already supported using the system properties that control the log dir
in the log4j.xml, data dir and tmp dir. See the admin guide for how the jboss
dist can be split up into different paths.
> Make the JBoss server runnable from a read-only partition
> ---------------------------------------------------------
>
> Key: JBAS-1224
> URL: http://jira.jboss.com/jira/browse/JBAS-1224
> Project: JBoss Application Server
> Type: Feature Request
> Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assignee: Scott M Stark
>
>
> SourceForge Submitter: didickman .
> In an enterprise setting, JBoss would be installed
> as /opt/jboss-3.2.x which would be a read-only area.
> The problem with the current setup of JBoss is that it
> expects to be able to write to /opt/jboss-3.2.x/server/
> {all,default,minimal}. Making JBoss instances easily
> accessible from a different area than /opt/jboss-
> 3.2.x/server/ is important in this environment and would
> be a very useful improvement.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
