From owner-freebsd-questions Mon Sep 20 13:31:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from Rigel.orionsys.com (rigel.orionsys.com [205.148.224.9]) by hub.freebsd.org (Postfix) with ESMTP id 74DDA1539D for ; Mon, 20 Sep 1999 13:31:44 -0700 (PDT) (envelope-from dbabler@Rigel.orionsys.com) Received: from localhost (dbabler@localhost) by Rigel.orionsys.com (8.9.3/8.9.3) with ESMTP id NAA27514 for ; Mon, 20 Sep 1999 13:31:31 -0700 (PDT) (envelope-from dbabler@Rigel.orionsys.com) Date: Mon, 20 Sep 1999 13:31:30 -0700 (PDT) From: David Babler To: FreeBSD Questions List Subject: ssh/xmalloc problem with 3.3-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a process that copies files from one machine to another as a cron job using rcp and ssh between two FBSD boxes. All has been working well for some time until this weekend when I updated the sender machine to 3.3-STABLE (CVSupped on Friday) from 3.2-STABLE. The recipient machine is a 3.2-STABLE box and now when I try to connect to it with ssh, it disconnects immediately with a syslog entry of: fatal: xmalloc: out of memory (allocating 1040068859 bytes) The wacko memory allocation comes up the same each time. Obviously something somewhere got hosed. I rebuilt the ssh(1) port again on the recipient machine to no effect. I can ssh from the 3.3 machine to itself with no problems... it just can't connect to the 3.2 machine now for some reason. Oddly, ssh on the 3.2 recipient machine reports as version 1.2.27 while the 3.3 machine's ssh (just rebuilt) says 1.2.26. Anybody have any idea what broke? TIA... -Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message