[7559] in Release_7.7_team
Re: Permission to use update hook?
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Tue Jul 26 21:39:50 2011
Date: Tue, 26 Jul 2011 21:39:44 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Jonathon Weiss <jweiss@mit.edu>
cc: Jonathan Reed <jdreed@mit.edu>, release-team@mit.edu
In-Reply-To: <201107270116.p6R1G9FA016919@outgoing.mit.edu>
Message-ID: <alpine.DEB.2.00.1107262137350.4814@tyger.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
I kind of actually want to see this run on all the machines so that we
know now (not during the semester and otherwise at a generally chill time)
if running a command of this form on the clusters all at once is a bad
idea.
--
Geoffrey Thomas
geofft@mit.edu
On Tue, 26 Jul 2011, Jonathon Weiss wrote:
>
> Is it worth coding this to explicitly only run on natty machines? I
> realize that the suggested fix should be a no-op everywhere else, but
> the paranoid in me says that scripts like this should touch as little as
> possible.
>
> Jonathon
>
>
> Jonathan Reed <jdreed@MIT.EDU> wrote:
>
>> Due to #987, there are now a number (3) of -development machines which can't take an update. This would be an ideal time to test out our update hook in real life, rather than waiting for a last resort. I propose trying out the following update hook:
>>
>> """
>> #!/bin/sh
>>
>> aptitude install debathena-auto-update
>> """
>>
>> This should be a no-op on production machines, and should pull in the new debathena-auto-update on -dev machines.
>>
>> Thoughts? We can also decide that the update hook should really truly only be reserved for the end of the world.
>>
>> -Jon
>
