[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[SAGE] Change control and patching for Linux
- To: SAGE mailing list <sage-members@xxxxxxxx>
- Subject: [SAGE] Change control and patching for Linux
- From: Jim Ankenbrandt <jim.ankenbrandt@xxxxxxxxx>
- Date: Wed, 02 Jan 2008 14:29:24 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=6Qqsha+K741klpSKyDkx/qVtqTL4ClagjNbG6aks+fs=; b=gXidqaGVcl5OaxfDVfGR6j8Ph/O+s3dRC0PJPvzGeY00E9sSEqU6uHzqJHySgwZelYANZPY07uPa7v8ozV4j0iW+yk2IRj0zTZotdv7rT2sBQ9uzFCbdYftWRmSWXT8cyKhVGdb1OWNiRfXk6EFYI1qHnLf5rKpIgQDyCPCYtDs=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=Y0UhRtiz+2b4cKb2isounz1h/SYx1oG/AXwopdReaNRL5z3GbgqilpRUEpqnO1lzAgOCidEUcJ6bL3hDsvP1pwVWHP0CKovwfOBVzORW9GyrA8hRPLL0ZZgE8GVSpFLPRwtvfNKLdWP2fjlMQ0TOJh0KgE+kxAuYv9r/VNcM3tA=
- Sender: owner-sage-members@xxxxxxxxxx
- User-agent: Thunderbird 1.5.0.14 (Windows/20071210)
I work for a bank in the American mid-west. Our data security group has
handed down a ruling that we need to begin a routine patching process.
Joy. By routine they mean a log of patches considered, reasons they
where rejected or passed, and a defined process to follow when
installing the patches. This will be subject to audit by the Fed's and
our internal groups.
Our environment is that we are running Red Hat Linux supporting Oracle
10g RAC clusters. The problem is that by the time we start a migration
from the certification cluster, test cluster, disaster recovery cluster,
to production cluster patches may have been outdated. What with change
windows, meetings with DBA's and sign offs it may take close to a month
to complete this path. Up2date is too blunt a tool, we cannot have
different levels on different clusters. We are considering installing
yum and defining our own repositories, but any experience or group
insight would be welcome
Jim Ankenbrandt