From owner-cvs-bin Sun Sep 28 14:33:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24113 for cvs-bin-outgoing; Sun, 28 Sep 1997 14:33:17 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24075; Sun, 28 Sep 1997 14:32:59 -0700 (PDT) Received: from panke.panke.de (anonymous221.ppp.cs.tu-berlin.de [130.149.17.221]) by mail.cs.tu-berlin.de (8.8.6/8.8.7) with ESMTP id XAA14066; Sun, 28 Sep 1997 23:25:39 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id XAA01260; Sun, 28 Sep 1997 23:23:45 +0200 (MET DST) To: Bruce Evans Cc: cvs-all@FreeBSD.ORG, cvs-bin@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/bin/mv mv.c References: <199709281130.VAA17274@godzilla.zeta.org.au> From: Wolfram Schneider Date: 28 Sep 1997 23:23:43 +0200 In-Reply-To: Bruce Evans's message of Sun, 28 Sep 1997 21:30:43 +1000 Message-ID: Lines: 18 Sender: owner-cvs-bin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans writes: > > $ touch from to > > $ echo -n loop | mv -i from to > > overwrite to? > > ^C > > You need more context in the example so that ^C doesn't kill mv. ^C intentionally killed mv(1) in the example above. What should you do with a process which eat all your CPU time? mv(1) print the message 'overwrite to? ' to stdout, read the characters 'l', 'o', 'o', 'p' from stdin, read 'EOF' from stdin and ignores it and try to read characters beyond EOF in an endless loop. -- Wolfram Schneider http://www.apfel.de/~wosch/