Adding the log4j configuration file available on https://github.com/Graylog2/graylog2-server

https://github.com/corey-hammerton/graylog2-rpms/issues/2

Will first add the unmodified log4j.xml file from the graylog2-server project to the SOURCE
directory. This file will be unused until such a time when documentation for externalizing
the log4j configurations for the graylog2-server and web-interface components.

In the meantime minor modifications to this file may be committed before it's included
in the init scripts and spec files to be built in the rpms.
Adding appenders graylog2-server and graylog2-web-interface to lgo4j.xml

https://github.com/corey-hammerton/graylog2-rpms/issues/2

In prepration for using the configuration file, adding individual appenders named
graylog2-server and graylog2-web-interface to log to /var/log/graylog2/. The
graylog2-server appender logs to ${dir}/server.log and the graylog2-web-interface
appender logs to ${dir}/web-interface.log.

Each appender is a DailyRollingFileAppender to rotate their respective log file
on a daily basis.
Merge branch 'master' into issue2
Adding new file log4j-graylog2-server.xml

https://github.com/corey-hammerton/graylog2-rpms/issues/2

The new file is an externalized version of the log4j.xml file that
comes pre-packaged in the graylog2-server package. In my experience
as a sysadmin this is only good for development/test environments,
come to production environments the sysadmins need control of the
logging. To monitor the application status and send log output to
the developers to investigate their code in order to fix any bugs or
other issues.

Will configure my test graylog2-server instance with a daily
rolling file appender to write to a self-managed log file instead
of to the currently configured stdout and redirecting to a file.
Merge branch 'master' into issue2
Adding an initial working log4j configuration to the main tree.

The primary appender in SOURCES/log4j-graylog2-server.xml is now
a DailyRollingFileAppender to write log entries to the file
/var/log/graylog2/server.log which is rotated everyday at midnight.

Uncommenting the ADDITIONAL_JAVA_OPTS variable in
SOURCES/sysconfig-graylog2-server in order to import the new log4j
configuration file in the graylog2-server service. It's content is
"-Dlog4j.configuration=file:///etc/graylog2/log4j-graylog2-server.xml"

Removing the stdout-to-file bash redirection in SOURCES/init.d-graylog2-server,
since the log4j configuration doesn't output to System.out/stdout
anymore.

Adding and installing a new source in SPECS/graylog2-server.spec,
source 4, for the log4j configuration file.
Add new file log4j-graylog2-web-interface.xml

https://github.com/corey-hammerton/graylog2-rpms/issues/2

As what was completed for the graylog2-server package, externalizing
the log4j configuration for the graylog2-web-interface must also
be completed. The contents of this file were taken from the
graylog2-web-interface documentation and modified to that the
behaviour mimics the graylog2-server configuration, even though the
classes here are different.

Initial testing for this configuration file needs to be completed
before I will include this file in the SPEC file.
Adding the log4j configuration for the web-interface to the main tree

Adding a sleep command in the result function of
SOURCES/init.d-graylog2-web-interface, because running a simple
stop and restart causing an exception because a port is already
in use because the services hasn't shut down yet before a start
was attempted.

Exiting with code 1 if the JAVA_CMD variable is not executable in
SOURCES/init.d-graylog2-web-interface

Removing the file redirection from the start command in
SOURCES/init.d-graylog2-web-interface. Since the new log4j config
no longer outputs to System.out/stdout a file redirection is not
needed.

Removing the commented classpath variable from
SOURCES/sysconfig-graylog2-web-interface, it contains the list of
individual jar files in the lib directory. Making this file another
thing to update on version updates, besides, any problems that may
occur for users will be based on their setup.

Including and installing the log4j-graylog2-web-interface.xml file
from SPECS/graylog2-web-interface.spec under /etc/graylog2/.
Officially adding it to the rpm building process.
Removing original logrotate source and spec file references.

https://github.com/corey-hammerton/graylog2-rpms/issues/2

Removing source file SOURCES/logrotate.d-graylog2 since logging
is now managed by log4j which is using it's own rotation
mechanism. There is no longer any technical reason to have a
server level logrotation process happening.

Removing all references to SOURCES/logrotate.d-graylog2 in
SPECS/graylog2-server.spec and SPECS/graylog2-web-interface.spec.
Did this by replacing source 3 with source 4 then removed all
lines that contained logrotate.

Removing the unsed SOURCES/log4j.xml file. This file was added when
this issue was initially create before any documentation for server
and web-interface logging was available.