From owner-freebsd-current Mon Jan 10 23:15:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id C515814E6B for ; Mon, 10 Jan 2000 23:15:26 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 15528 invoked from network); 11 Jan 2000 07:15:25 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 11 Jan 2000 07:15:25 -0000 Message-ID: <387AD873.1814A5F9@cvzoom.net> Date: Tue, 11 Jan 2000 02:14:59 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Schneiders Cc: current@freebsd.org Subject: Re: ssh2: piperd = hanging? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Schneiders wrote: > > Trying to use cvs to get a working copy of /usr/src from the > /home/ncvs of one machine to another, cvs just hangs. Top displays as > state for cvs `piperd'. I have not been able to find this documented > in the top man page. A guess: pipe reading data? In my case it > indicates cvs or ssh hanging :-( There are no data read anymore in any > case (for which top seems to print `getblk' or `RUN' during the short > time cvs works). Things remain like this until I kill cvs through ^C. `piperd' means a process is reading from a pipe. In your case, maybe reading from a pipe is causing a hang. Of course, the inverse of piperd is pipewt, I believe, which means the process is writing to a pipe. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message