You can always just ignore the files in git, but yes the better solution
is to find out why your logs are not properly routed to var/log.
Andy.
On 13/08/2014 11:54, helio frota wrote:
Hi Daniel,
you mean log information such as sysout and syserr will be written to logs
specific to the Automatic Bug-Reporting Tool [1]?
Yes.
If so could you try to investigate how such information could be re-routed
to "proper" logs under
/var/log ?
Ok, i guess i can found this.
Just as an additional remark - Simply stopping a system service might not
be what everybody wants cause other services might depend on the just
deactivated service or peeps actually keopt the service active
intentionally.
Yes you right, the main problem is the logs appears on source code
directories causing unmanaged files on git and/or svn.
thanks
On Wed, Aug 13, 2014 at 3:53 AM, dsh <[email protected]> wrote:
Hi Helio,
you mean log information such as sysout and syserr will be written to logs
specific to the Automatic Bug-Reporting Tool [1]? If so could you try to
investigate how such information could be re-routed to "proper" logs under
/var/log ? I think one purpose of a proper package for a particular OS
distribution is taking care of such nitty gritty stuff to be placed at a
proper, OS compliant location.
Just as an additional remark - Simply stopping a system service might not
be what everybody wants cause other services might depend on the just
deactivated service or peeps actually keopt the service active
intentionally.
[1]
http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/ch-abrt.html
Cheers
Daniel
On Wed, Aug 13, 2014 at 4:19 AM, helio frota <[email protected]> wrote:
hi all,
take care about fedora abrt logs.
when i try to do a package of tomEE a lot of logs appears here.
you can disable this as root
systemctl abrtd stop
systemctl disable abrtd.service
let us know if it worked.
thanks
