On 04/13/2012 06:41 PM, Itamar Heim wrote:
>>> # Let's copy the logging.properties
>>> cp /usr/share/jboss-as/standalone/configuration/logging.properties
>>> configuration/
>>> # Let's copy the mgmt-users.properties
>>> cp /usr/share/jboss-as/standalone/configuration/mgmt-users.properties
>>> configuration/
>>> # Copy standalone.xml
>>> cp /usr/share/jboss-as/standalone/configuration/standalone-web.xml
>>> configuration/
>>
>> are these considered .conf files under /etc?
>> if not, what happens on yum update of jboss, which will not update these
>> files?
>
> In general above example is for users not interested in storing anything
> in /etc.
>
> But yes, in your case all above files are stored (for example) in
> /etc/ovirt-engine/jboss-as/ dir and it's symlinked to the configuration/
> dir in $JBOSS_BASE_DIR.
>
> Does it make sense?
my question was actually if the original files are being updated via yum
update, since now we'd be using copies.
You're shipping your configuration files and therefore you're
maintaining these files. Above cp commands were just an example how to
quick-start.
Original files stored in /etc/jboss-as/standalone are not used at all
when starting AS in the way I presented above. They can be changed and
it'll not make any difference to your environment. More, they can be
even removed and your service will still work.
--Marek