Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 34E0310B11 for ; Tue, 8 Oct 2013 14:00:35 +0000 (UTC) Received: (qmail 79817 invoked by uid 500); 8 Oct 2013 14:00:31 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 79699 invoked by uid 500); 8 Oct 2013 14:00:30 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 79690 invoked by uid 99); 8 Oct 2013 14:00:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 14:00:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sharkymail@gmail.com designates 209.85.223.170 as permitted sender) Received: from [209.85.223.170] (HELO mail-ie0-f170.google.com) (209.85.223.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 14:00:22 +0000 Received: by mail-ie0-f170.google.com with SMTP id x13so20159249ief.29 for ; Tue, 08 Oct 2013 07:00:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zwTAN7JXErDkODlHlF+mwCJhTmYUaWl8YZ/4LHdB8r4=; b=x2keng4P/weJFtMsXrzzB7LRUtbo0Oj+NucBOYQSxV8I+bjnIPMLcLch6KcCBu10dZ gY1fop8PEadbsnEVd/WfqcJmUeD9DNn9Xqt5EsgzBjEsMQLzszcLce0prD/eq23Gt9zS PZCI9+qveLyMHtPOlWpKP1NKiWl63KUYvHIwbzqhQG9Juo6XUg2OpDgBu8W2nGdpXoQF Z72XiOk+lHebom4a/EhXNz5LQY0kPOKatmsxXrgXH2yzLFildwHhJw3YQemMB9fLYQJl OzWhS8sNqI99fV080PpQguerl1YI0hhOdx3UkdBtr/M+mYlcvAU1Eaqhthwd6Z/mUCDs WQyQ== MIME-Version: 1.0 X-Received: by 10.43.132.66 with SMTP id ht2mr1205686icc.26.1381240801740; Tue, 08 Oct 2013 07:00:01 -0700 (PDT) Received: by 10.50.217.133 with HTTP; Tue, 8 Oct 2013 07:00:01 -0700 (PDT) Date: Tue, 8 Oct 2013 15:00:01 +0100 Message-ID: Subject: Override logging From: Geoff Meakin To: users@tomcat.apache.org Content-Type: multipart/alternative; boundary=20cf307f31fe5650b304e83b2ff7 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f31fe5650b304e83b2ff7 Content-Type: text/plain; charset=ISO-8859-1 I've been asked to host a couple of tomcat thirdparty webapps which all have either logging.properties or log4j configurations (internally). My question is, as a sysadmin who only gets to run the tomcat container, can I override all the logging configurations of my apps. For example, I dont use disks to log, I use syslog, and want to force all tomcat logs to go over syslog. I've read all the docs on JULI and log4j, and my head has exploded, and I appreciate there are ways to do this in the properties file of the app itself. However, I can't change the apps, and want to override all at the container level. Is this possible? I can't imagine that it wouldn't be. Hope this isn't too much of a n00b question. --20cf307f31fe5650b304e83b2ff7--