From owner-freebsd-questions@FreeBSD.ORG  Mon Aug 18 21:12:50 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 50819C6
 for <freebsd-questions@freebsd.org>; Mon, 18 Aug 2014 21:12:50 +0000 (UTC)
Received: from server1.shellworld.net (shellworld.net [69.60.117.94])
 by mx1.freebsd.org (Postfix) with ESMTP id 2DCD33831
 for <freebsd-questions@freebsd.org>; Mon, 18 Aug 2014 21:12:49 +0000 (UTC)
Received: from server1.shellworld.net (localhost [127.0.0.1])
 by server1.shellworld.net (Postfix) with ESMTP id 0EEDB22957
 for <freebsd-questions@freebsd.org>; Mon, 18 Aug 2014 17:07:21 -0400 (EDT)
To: "FreeBSD Questions !!!!" <freebsd-questions@freebsd.org>
Subject: What Would Make Sudo Always Let one Execute a Command?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <48925.1408396040.1@server1.shellworld.net>
Date: Mon, 18 Aug 2014 16:07:21 -0500
From: "Martin G. McCormick" <martin@server1.shellworld.net>
Message-Id: <20140818210721.0EEDB22957@server1.shellworld.net>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Aug 2014 21:12:50 -0000

Sudo behaves as if the default timeout in sudoers was set to -1.
Out of 5 FreeBSD9 systems, this one system exhibits this
behavior while all the others time out like they should. Setting
the value to 0 should cause one to always have to enter a
password, but not on this system.
	Has anyone ever seen this before? The sudoers file is a
copy of the same sudoers file we use on the other machines. I
have also tried sudo from a few other user ID's on the system
and see the same behavior.
Thank you.

Martin McCormick