From owner-freebsd-questions@FreeBSD.ORG  Sat Jul 28 12:58:05 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1881716A418
	for <freebsd-questions@freebsd.org>;
	Sat, 28 Jul 2007 12:58:05 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219])
	by mx1.freebsd.org (Postfix) with ESMTP id E2F1B13C46C
	for <freebsd-questions@freebsd.org>;
	Sat, 28 Jul 2007 12:58:02 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.13.8/8.13.8) with ESMTP id l6SCw2SB065492
	for <freebsd-questions@freebsd.org>;
	Sat, 28 Jul 2007 07:58:02 -0500 (CDT)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200707281258.l6SCw2SB065492@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
Date: Sat, 28 Jul 2007 07:58:02 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Re: Remote Execution of sudo Command Hangs. 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Sat, 28 Jul 2007 12:58:05 -0000

"Christian Walther" writes:
> Try using "pseudo tty allocation" with your ssh command, it's the "-t" 
> option.
> So, use "ssh -t remote.system.domain sudo dhcpreset" as the command.

That worked perfectly.

> If this doesn't work directly, you can even try several "t"s. I had
> best results with -ttt.

	This is great to know. The only difference besides the
fact it now works is that one sees a closed-connection message
like what you see when you ssh to another system and spawn a
shell because that seizes tty's also.

	It just hadn't occurred to me before that you don't
seize a tty on the remote system when you remotely run an ssh
command.

Martin McCormick WB5AGZ  Stillwater, OK 
Systems Engineer
OSU Information Technology Department Network Operations Group