From owner-freebsd-stable@FreeBSD.ORG Sat Apr 19 22:24:47 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D6D424D3 for ; Sat, 19 Apr 2014 22:24:47 +0000 (UTC) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3761895 for ; Sat, 19 Apr 2014 22:24:47 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id w8so2693308qac.12 for ; Sat, 19 Apr 2014 15:24:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=5H/h33zSChIWBfVYVA3jtF4jA72H6MYwjAeROc5Oh7g=; b=ZIuttANYPoJXJh9bJghSS/qjUPLnGf2Shd7mYlAEoPbalOYcA4PlJCdJio/Kv1n+x2 xYtrHtrI2j3vc0kk4Og7kMhO585EESZ5b6gAxNGxGG8HizrpokP39VsR57EVP4Mu5L0M Vz+MSxOYC1TYfiaG16JZ2GnLh3TWclMtznUNPUUbjb6iCslcEl0rTBUwMjP4MfN5eTnS lTdjOFo0BsgCmWSwYV+6zAQ1JaG3/eib2Z6rdcYu1OjNy5ukkSrv9Zl8hEQn+ZZ233Kl B53NqD+HFLK98jGUvRYwANyowAKuMGkRPWuRzAMbkulJNwMEFLHakBLz9OZ3kTopmMT9 GObA== X-Received: by 10.224.161.83 with SMTP id q19mr28686022qax.56.1397946286820; Sat, 19 Apr 2014 15:24:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.180.68 with HTTP; Sat, 19 Apr 2014 15:24:26 -0700 (PDT) From: James Welcher Date: Sat, 19 Apr 2014 15:24:26 -0700 Message-ID: Subject: Syslogd question To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2014 22:24:47 -0000 Hi, possibly quick and perhaps subtle question about syslogd. I have a machine that is a syslog server (receives network logs from other hosts), but also a syslog client (sends logs over the network to yet another syslog server). How can I configure the server to locally log the network connections it receives, but NOT to forward these remotely received messages? In the old days, this was called "hopping." I think this kind of forwarding of remote entries was PREVENTED by default. It had to be enabled with the "-h" (hop) option. Anyone know how I can prevent syslogd from hopping/remote forwarding nowadays? -- James Welcher