From owner-freebsd-stable@FreeBSD.ORG Thu Feb 5 18:27:27 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7CD96448 for ; Thu, 5 Feb 2015 18:27:27 +0000 (UTC) Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ftp.orthanc.ca", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49B5A605 for ; Thu, 5 Feb 2015 18:27:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by orthanc.ca (8.14.7/8.14.7) with ESMTP id t15IRO4T094358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Feb 2015 10:27:24 -0800 (PST) (envelope-from lyndon@orthanc.ca) Date: Thu, 5 Feb 2015 10:27:24 -0800 (PST) From: Lyndon Nerenberg To: =?ISO-8859-2?Q?Marko_Cupa=E6?= Subject: Re: push a few config files to dozen or so servers In-Reply-To: <20150205130234.3fcbabfb@efreet.mimar.rs> Message-ID: References: <20150205130234.3fcbabfb@efreet.mimar.rs> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) Organization: The Frobozz Magic Homing Pigeon Company MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 18:27:27 -0000 > I was looking at puppet and cfengine but learning and implementing those > seem like an overkill for my purpose. > > Are there any other elegant solutions which can help me achieve my goal? rdist. It used to be in the base system, but was moved to ports for specious security paranoia reasons. Set the appropriate environment variable to have it use ssh(1) instead of rsh(1) and you're good to go. --lyndon