From owner-freebsd-questions@FreeBSD.ORG Wed Jan 22 19:47:06 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 079C4C0F for ; Wed, 22 Jan 2014 19:47:06 +0000 (UTC) Received: from x.it.okstate.edu (x.it.okstate.edu [139.78.2.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2D221CB6 for ; Wed, 22 Jan 2014 19:47:05 +0000 (UTC) Received: from x.it.okstate.edu (localhost [127.0.0.1]) by x.it.okstate.edu (8.14.5/8.14.5) with ESMTP id s0MJWAtk073598 for ; Wed, 22 Jan 2014 13:32:10 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <201401221932.s0MJWAtk073598@x.it.okstate.edu> From: Martin McCormick cc: freebsd-questions@freebsd.org Subject: Unusual Exit Behavior MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <73596.1390419130.1@x.it.okstate.edu> Date: Wed, 22 Jan 2014 13:32:10 -0600 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: Wed, 22 Jan 2014 19:47:06 -0000 The strangest thing just happened on a FreeBSD9.1 system. I had used ssh to access this system in command-line mode from a Linux platform running screen so it is possible that the behavior came from either the Linux box or the FreeBSD system but here is what happened. I was on the FreeBSD system in bash, testing a perl script I was writing and I called calc to tell me the answer to a simple subtraction problem. It gave me the answer but then there was no shell prompt. Thinking this was odd, I hit Return a couple of times with nothing so I typed Control-C and got a message stating something like "abort level 1." Each Control-C I typed incremented the abort level until at about 3 or 4, I did get the shell prompt back. Every time I ran calc, I got that behavior. I could short-circuit the odd exit by typing Control-D, but calc wouldn't just end like it always does if you type something like calc 86400-3600 I finally caused screen on the Linux box to exit, killing all the open sessions and when I restarted screen again and re-connected to the same FreeBSD box, everything was totally back to normal. I am pretty sure I set something that thankfully unset after the logout, but what could it have been? I don't really think this had anything to do with calc but at this stage, I would believe just about anything. I have been using unix for about 22 years and I am not sure I have ever seen this before. Martin McCormick