From owner-freebsd-questions@FreeBSD.ORG Sun Mar 23 09:17:54 2014 Return-Path: Delivered-To: freebsd-questions@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 EE1AEB28 for ; Sun, 23 Mar 2014 09:17:54 +0000 (UTC) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C5598278 for ; Sun, 23 Mar 2014 09:17:54 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id rp16so4196069pbb.12 for ; Sun, 23 Mar 2014 02:17:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=uaH8nxhj0xUMTmwwtf8R/rXalCtDfJP2tWvpA035/Ig=; b=sAlVENzbOZcda2Q2M4hIJ1XY9GrotZV8sjNH6htSJw2t8lR1/sGPqRlGQ6JHXSFrC0 NONktzM9vRM2B5usfghB+tQdNz1uPmoCEL2Sz5hly1HD2CQAOv5AXKDwg8iWJPCSnZSZ vwX4P+LMsSvgznfSdMDiTDwR/CritDr3ZNpYhdT1n4/5Qo5ThK2E5CRzK1gIVUFLFTjC TX1ziejW84EzqN4WDEBz70AMAPfJVQRxoPGqRqoxJKsRsSECiwDwbqG6H6BwrG3pyJZ8 hoUaCaBQhXTZ9Q+KYNRZtitZRT9Z3x571Djl8jvP1UooBNgQypWheWuDaG8GSlZkO/vx +GRg== X-Received: by 10.68.233.37 with SMTP id tt5mr478148pbc.154.1395566274462; Sun, 23 Mar 2014 02:17:54 -0700 (PDT) Received: from SergeiMBP.local (c-67-185-33-48.hsd1.wa.comcast.net. [67.185.33.48]) by mx.google.com with ESMTPSA id ac5sm20983797pbc.37.2014.03.23.02.17.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Mar 2014 02:17:53 -0700 (PDT) Message-ID: <532EA6BF.6030008@gmail.com> Date: Sun, 23 Mar 2014 02:17:51 -0700 From: Sergei G User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: rc.d script suppression of messages in sshguard Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Mar 2014 09:17:55 -0000 I had sshguard configured through rc.conf which effectively puts it into daemon mode. I then reconfigured sshguard and introduced invalid configuration option that made it fail to start. Unfortunately /usr/local/etc/rc.d/sshguard is configured to start daemon with -f option, which suppresses any STDOUT messages by sending those to /dev/null. I learned about all of this only after I have removed -f option in sshguard script itself. Suddenly, I was able to read error message from sshguard with statement "Terminating". It now could explain why my service was not listed with ps -x | grep sshguard. Is this issue something that can be requested to be fixed? How do I do that if you think it is worth it. I have noticed the side effect of my change. I had to press Enter to get my prompt back after I issued "service sshguard start".