From owner-freebsd-hackers  Mon Feb  5 13:26:24 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA25945
          for hackers-outgoing; Mon, 5 Feb 1996 13:26:24 -0800 (PST)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA25933
          for <hackers@freebsd.org>; Mon, 5 Feb 1996 13:26:19 -0800 (PST)
Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id NAA26300; Mon, 5 Feb 1996 13:20:37 -0800
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199602052120.NAA26300@ref.tfs.com>
Subject: Re: And the winner is!
To: ath@bellcore.com (Andrew Heybey)
Date: Mon, 5 Feb 1996 13:20:36 -0800 (PST)
Cc: dfr@render.com, karl@mcs.com, jkh@time.cdrom.com, hackers@freebsd.org
In-Reply-To: <199602051522.KAA02892@grapenuts.bellcore.com> from "Andrew Heybey" at Feb 5, 96 10:22:05 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
Precedence: bulk

 We do this on our production sites at TFS (not at pouls's site though :)

All machines SUP everything at boot
and  applications are SUP'd on operator sign-on in some
cases as well. (e.g. keing stateions.. log off and log on
to get newer versions of the app. (naturally
there is USUALLY nothing to get)
> 
>   dfr> It seems like one could use sup to keep systems in sync.
>   dfr> Basically, you would run a supserver on the 'code server' and
>   dfr> regularly sup the client systems against it.  The sup config
>   dfr> files allow you to do stuff like run ranlib on /usr/lib/lib*.a,
>   dfr> execute newaliases when /etc/aliases changes, don't take
>   dfr> specific files from /etc/ which are per-system.
> 
> Yes, sup would work and has some advantages (for one thing reconcile
> needs the server to be NFS mounted).  For me it was a matter of being
> familiar with reconcile.  Also, reconcile does several things that I
> don't know if sup can do:
> 
>