Bug 1002967 - appclient does not log to /var/log
Summary: appclient does not log to /var/log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RPMs
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: ---
Assignee: Permaine Cheung
QA Contact: Katerina Odabasi
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-30 11:33 UTC by Aleksandar Kostadinov
Modified: 2015-02-20 11:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL6 RPM
Last Closed: 2013-12-15 16:22:57 UTC
Type: Bug


Attachments (Terms of Use)

Description Aleksandar Kostadinov 2013-08-30 11:33:22 UTC
Running appclient.sh in RPM installation does not put log files in /var/log like standalone and domain servers but in /usr/share/jbossas/appclient/log

This is inconsistent with the other two modes of operation as well incorrect with regard to RHEL directory layout guidelines.

Comment 1 Permaine Cheung 2013-10-07 13:01:54 UTC
The fix has been included in ER5.
For new installation of jbossas-appclient, log/ symlinks to /var/log/jbossas/appclient, and tmp/ symlinks to /var/cache/jbossas/appclient, we don't change existing installation during any upgrade as user may already have things set up as they want to work with their applications and we don't want to change that behind their back.

Comment 2 Aleksandar Kostadinov 2013-10-07 13:11:47 UTC
Do I understand correctly that yum update will *not* introduce the change even if user never started appclient? For example yum update on our latest EAP6 EC2 AMIs will still end-up with appclient logging to /usr/share?

Comment 3 Permaine Cheung 2013-10-08 18:07:06 UTC
Correct, any changes like this is best to take place in a fresh installation, with any existing installation, it's not a good idea to change things like this over an upgrade.

Comment 4 Aleksandar Kostadinov 2013-10-15 14:45:00 UTC
tested with ER5


Note You need to log in before you can comment on or make changes to this bug.