From owner-freebsd-bugs Tue Jul 20 7:20: 4 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 537AD15175 for ; Tue, 20 Jul 1999 07:20:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id HAA29745; Tue, 20 Jul 1999 07:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 20 Jul 1999 07:20:02 -0700 (PDT) Message-Id: <199907201420.HAA29745@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bob Willcox Subject: Re: bin/12496: yppush broken when pushing to 2 or more slaves Reply-To: Bob Willcox Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/12496; it has been noted by GNATS. From: Bob Willcox To: freebsd-gnats-submit@freebsd.org, andre.albsmeier@mchp.siemens.de Cc: Subject: Re: bin/12496: yppush broken when pushing to 2 or more slaves Date: Tue, 20 Jul 1999 09:14:21 -0500 I to, am seeing this problem (though I have only one slave). The system I am running yppush on (the master) is: FreeBSD obiwan.pmr.com 3.2-STABLE FreeBSD 3.2-STABLE #10: Sun Jun 27 14:00:22 CDT 1999 bob@obiwan.pmr.com:/usr2/src/sys/compile/OBIWAN i386 Ifdef'ing out the two lines set_program_var lines mentioned by Andre works around (or hides) the problem for me. Bob -- Bob Willcox Don't tell me that worry doesn't do any good. bob@pmr.com I know better. The things I worry about don't Austin, TX happen. -- Watchman Examiner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message