| Summary: | appclient does not log to /var/log | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Aleksandar Kostadinov <akostadi> |
| Component: | RPMs | Assignee: | Permaine Cheung <pcheung> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Katerina Odabasi <kanovotn> |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | pcheung, pgier |
| Target Milestone: | ER5 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
RHEL6 RPM
|
|
| Last Closed: | 2013-12-15 16:22:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Aleksandar Kostadinov
2013-08-30 11:33:22 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. 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? 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. tested with ER5 |