[mythtvnz] Hardy updates breaks schedule

[Nick Rout]

On Mon, Jun 30, 2008 at 12:52 PM, David Lowe <david at thistledown.co.nz> wrote:
> On Mon, Jun 30, 2008 at 12:20 PM, Nick Rout <nick.rout at gmail.com> wrote:
>>
>> This does seem to support the first rule of mythtv maintenance:
>>
>> "Do not mess with a system that is running well"
>>
>
> ... which is good advice, but updates come down from Ubuntu almost every
> day. What's a security conscious guy gonna do?

To that I would say, what security threats are you exposing your
mythbox to? It should be well hidden from the net behind a firewall (I
have been known to want access to mythweb from work and I go through a
rigmarole of opening a port in my firewall remotely, accessing
mythweb, then closing the hole).


>
> Barry are you sure it was the update that stopped the database running? What
> would you do differently next time? (And I doubt anybody minds you posting
> your own replies; I for one have been following you intently, being about to
> run an upgrade.)

I am still confused about whether Barry did have a full filesystem,
which could have been caused by the update files piling up in
/var/cache/apt/ (is that the right path? its close). Anyway I guess if
the system ran out of space during an update something untoward might
have happened. Like the --reconfigure part not running. Which would be
why it started working after you ceared some disk space and ran it
manually.

Just conjecture and semi-educated guesswork here.

Rule 2 of myth maintenance: "get more hard drive space yesterday."