From owner-freebsd-questions@FreeBSD.ORG Fri Nov 1 03:30:21 2013 Return-Path: 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 ESMTP id D0E31E04 for ; Fri, 1 Nov 2013 03:30:21 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 95A1927B4 for ; Fri, 1 Nov 2013 03:30:21 +0000 (UTC) Received: from r56.edvax.de (port-92-195-117-74.dynamic.qsc.de [92.195.117.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 1D6023CBB4; Fri, 1 Nov 2013 04:30:20 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id rA13UAvA003164; Fri, 1 Nov 2013 04:30:10 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Fri, 1 Nov 2013 04:30:10 +0100 From: Polytropon To: Martin McCormick Subject: Re: Inputs and outputs in the right order Message-Id: <20131101043010.c1cc84e3.freebsd@edvax.de> In-Reply-To: <201311010256.rA12u1jx009134@x.it.okstate.edu> References: <201311010256.rA12u1jx009134@x.it.okstate.edu> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 03:30:21 -0000 On Thu, 31 Oct 2013 21:56:01 -0500, Martin McCormick wrote: > I know that expect does a great job of logging a session > but I am wondering if there is an easier way to get the shell > input echoed interwoven with all the output. In shorter words, > what is the easiest way to produce a session log that reads like > what actually happened when it happened? Without knowing anything about the design of the script and its input, I'd guess that something like | tee or maybe even /usr/bin/script could work? It highly depends on what is being echoed / printed to stdout and stderr and how the script deals with the inputs... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...