Timothy,
> -Original Message-
> The problem is that the server is a long way away (in another country)
> and I won't have any way of contacting it if it stops running.
--
If your system is half-way around the world (or even half-way around the state),
you might consider investing and inst
Johnny Hughes wrote:
>> Johnny Hughes suggested the command, so on that basis alone
>> I would give it a high probability of success.
>
> If you have ALL the latest glibc/nscd files to replace all the installed
> RPMS in the same place, and if you upgrade them all at the same time
> (including an
On 05/27/2012 06:03 AM, Timothy Murphy wrote:
> John Stanley wrote:
>
> Now this is my last question:
> Can I be reasonably (say 90%) sure that the above command
> will not stop the server running?
>>> The command in question was: rpm -Uvh --force *.rpm
>>> where the RPMs were glibc and
Les Mikesell wrote:
> I've had yum sessions fail (probably mostly from starting them in a
> freenx session...) but never to the point where
> yum-complete-transaction did not fix it, so I don't have a good
> feeling for what is actually happening. However, I wouldn't expect a
> forced install of a
On Sun, May 27, 2012 at 6:03 AM, Timothy Murphy wrote:
>
>>> > Wait and schedule a downtime window for it.
>>>
>>> I don't know what a "downtime window" is in this context.
>>> I'm either in the same place as the server, or I am not.
>>
>> Downtime Window: It's when you schedule a specific time t
John Stanley wrote:
>> >> Now this is my last question:
>> >> Can I be reasonably (say 90%) sure that the above command
>> >> will not stop the server running?
>>
>> The command in question was: rpm -Uvh --force *.rpm
>> where the RPMs were glibc and glibc-common.
>>
>> > No you can NOT and don'
On Sun, 2012-05-27 at 01:01 +0100, Timothy Murphy wrote:
> John Stanley wrote:
>
> >> Now this is my last question:
> >> Can I be reasonably (say 90%) sure that the above command
> >> will not stop the server running?
>
> The command in question was: rpm -Uvh --force *.rpm
> where the RPMs were g
John Stanley wrote:
>> Now this is my last question:
>> Can I be reasonably (say 90%) sure that the above command
>> will not stop the server running?
The command in question was: rpm -Uvh --force *.rpm
where the RPMs were glibc and glibc-common.
> No you can NOT and don't ever assume that.
>
On Sat, 2012-05-26 at 12:45 +0100, Timothy Murphy wrote:
> Now this is my last question:
> Can I be reasonably (say 90%) sure that the above command
> will not stop the server running?
No you can NOT and don't ever assume that. That's a mistake thinking
that.
> The problem is that the server is
Johnny Hughes wrote:
> Based on your errors, what I would do is this:
Thanking you again for all your help.
I have one last question, and then I promise to ask no more!
Could the rpm --force suggestion you make possibly stop the server working?
> 1. You only need 1 version of glibc-common.x86_
m.r...@5-cent.us wrote:
>> I think I understand how it occurred.
>> I tried to yum-remove a package
>> (I don't remember which one, but it wasn't important)
>> and I was told that 300+ packages would be removed.
>> I wasn't sure it I would be asked yes/no to this
>> (I know now that I will always
Tim,
Timothy Murphy wrote:
> Johnny Hughes wrote:
>> On 05/23/2012 04:41 PM, Timothy Murphy wrote:
>>> Johnny Hughes wrote:
>> 3. The real issue here is to make sure you figure out HOW you got in
>> this position and how NOT to get into it again.
>
> I think I understand how it occurred.
> I tri
Johnny Hughes wrote:
First, thanks very much for continuing to help me.
> On 05/23/2012 04:41 PM, Timothy Murphy wrote:
>> Johnny Hughes wrote:
>>
---
Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
glibc-2.12-1.47.el6_2.9.i686
>>>
On 05/23/2012 04:41 PM, Timothy Murphy wrote:
> Johnny Hughes wrote:
>
>>> ---
>>> Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
>>> glibc-2.12-1.47.el6_2.9.i686
>>> ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
>>> bash-4
Johnny Hughes wrote:
>> ---
>> Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
>> glibc-2.12-1.47.el6_2.9.i686
>> ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
>> bash-4.1.2-9.el6_2.x86_64 is a duplicate with
>> bash-4.1.2-
On 05/22/2012 05:05 AM, Timothy Murphy wrote:
> Is anyone getting a yum update problem with glibc and glibc-common?
> I'm getting the error message
> ---
> Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
> glibc-2.12-1.47.el6_2.9.i686
> ** Found 3
Is anyone getting a yum update problem with glibc and glibc-common?
I'm getting the error message
---
Error: Protected multilib versions: glibc-2.12-1.47.el6_2.12.x86_64 !=
glibc-2.12-1.47.el6_2.9.i686
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows
17 matches
Mail list logo
