> Environment
>
> Red Hat Enterprise Linux(RHEL) 6.3
> autofs-5.0.5-54.el6.x86_64
> --
>
> This leads me to believe that upstream is aware of this issue and
> someone there is working on a fix.
I was reading your posts with Joerg Sch
Hello,
The latest update to sudo (sudo-1.7.2p1-14.el5_8.2) breaks postgresql.
https://bugzilla.redhat.com/show_bug.cgi?id=846631
It might break other services that rely on access to /etc/nsswitch.conf
too. Assuming you have a "sudoers" line in /etc/nsswitch.conf that file
will be recreated with
On Wed, 2012-08-08 at 19:25 -0400, Cal Webster wrote:
> On Wed, 2012-08-08 at 18:37 -0400, Cal Webster wrote:
> > See Red Hat Bugzilla bug #846852 for details.
> > https://bugzilla.redhat.com/show_bug.cgi?id=846852
>
> This leads me to believe that upstream is aware of this issue and
> someone the
On Thu, 2012-08-09 at 12:21 +0200, Leonard den Ottolander wrote:
> The latest update to sudo (sudo-1.7.2p1-14.el5_8.2) breaks postgresql.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=846631
>
> It might break other services that rely on access to /etc/nsswitch.conf
> too.
I should have mentio
On Thu, 2012-08-09 at 10:35 +0100, Lars Hecking wrote:
> > Environment
> >
> > Red Hat Enterprise Linux(RHEL) 6.3
> > autofs-5.0.5-54.el6.x86_64
> > --
> >
> > This leads me to believe that upstream is aware of this issue and
> > someone
On 08/09/2012 05:21 AM, Leonard den Ottolander wrote:
> Hello,
>
> The latest update to sudo (sudo-1.7.2p1-14.el5_8.2) breaks postgresql.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=846631
>
> It might break other services that rely on access to /etc/nsswitch.conf
> too. Assuming you have a "su
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ..
>> These could be bad options for a number of users and since it's set at
>> kernel boot time how can you override it once the OS has booted? Can you
>> disable this without altering boot parameters and rebooting? If the answer
>> is yes than a tuned configuration should be created or altered
I have just installed 6.3 on a machine that was previously running
5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
static IP as I intend to for this to be machine used on my LAN only.
However, when I do /u
On Thu, Aug 09, 2012 at 12:33:43PM -0500, Richard Reina wrote:
> I have just installed 6.3 on a machine that was previously running
> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
> static IP as I inte
Scott Robbins wrote:
> On Thu, Aug 09, 2012 at 12:33:43PM -0500, Richard Reina wrote:
>> I have just installed 6.3 on a machine that was previously running
>> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
>> wlan0 and p4p1 (instead of eth0). I would like to make the ethern
If it's as simple as sticking the MAC address into the ifcfg-eth file,
I can live with that. But only ifcfg script that exits in
/etc/sysconfig/network-scripts/ is ifcfg-lo
I have no idea what k3wl is.
Thanks for the replies.
2012/8/9, m.r...@5-cent.us :
> Scott Robbins wrote:
>> On Thu, Aug 09
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error "Cannot access the hardware clock
by any known method", and then promptly sets the time 5 hours behind
the hardware clock, down to the second.
After the system is up. "hwclock" works f
Hi,
Anybody on the list running CentOS 6.3 on the above. If so do you have HP psp
9.10 installed
and working without getting the following error?
cmahealthd[4406]: segfault at f ip 009ff06d sp bfb6fdc4 error 4 in
libc-2.12.so[98e000+18c000]
Do you have any version of the psp working without err
Richard Reina wrote:
> If it's as simple as sticking the MAC address into the ifcfg-eth file,
> I can live with that. But only ifcfg script that exits in
> /etc/sysconfig/network-scripts/ is ifcfg-lo
>
> I have no idea what k3wl is.
Script-kiddie speak. 3 == e. I was being sarcastic (about the fed
Russell Jones wrote:
> Hi all,
>
> I am having an issue with some older CentOS 5.3 servers. Every time
> the server boots, it gives the error "Cannot access the hardware clock
> by any known method", and then promptly sets the time 5 hours behind
> the hardware clock, down to the second.
>
So, it's
Thanks for the reply.
The hwclock can be set properly from the OS. No BIOS permissions to
even set for the clock, it's just a standard old 24 hour clock.
On Thu, Aug 9, 2012 at 2:43 PM, wrote:
> Russell Jones wrote:
>> Hi all,
>>
>> I am having an issue with some older CentOS 5.3 servers. Ever
On Aug 9, 2012, at 12:33 PM, Russell Jones wrote:
> Hi all,
>
> I am having an issue with some older CentOS 5.3 servers. Every time
> the server boots, it gives the error "Cannot access the hardware clock
> by any known method", and then promptly sets the time 5 hours behind
> the hardware clock
On Thu, Aug 9, 2012 at 1:47 PM, wrote:
>
>>> I have just installed 6.3 on a machine that was previously running
>>> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
>>> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
>>> static IP as I intend to for th
Thanks, I tried again, rebooted, still 5 hours off slow. The second I
do "hwclock --hctosys" the time is fine. That's silly to have to do
that though, I feel like I am missing a configuration parameter
somewhere.
[root@nod705 ~]# date
Thu Aug 9 10:06:36 CDT 2012
[root@nod705 ~]# hwclock
Thu 09
until you set your clock so that 'date' gives the right time, don't bother
doing anything else. Once you get it set, then execute the hwclock --systohc
Craig
On Aug 9, 2012, at 1:08 PM, Russell Jones wrote:
> Thanks, I tried again, rebooted, still 5 hours off slow. The second I
> do "hwclock --
Craig,
Let me clarify. I correct the time, and both "date" and "hwclock" both
show the correct time. I reboot the server and "date" is again 5 hours
slow.
On Thu, Aug 9, 2012 at 3:22 PM, Craig White wrote:
> until you set your clock so that 'date' gives the right time, don't bother
> doing
I installed off the live CD. I will try a 6.3 net install and see what changes.
El Aug 9, 2012, a las 2:40 PM, m.r...@5-cent.us escribió:
> Richard Reina wrote:
>> If it's as simple as sticking the MAC address into the ifcfg-eth file,
>> I can live with that. But only ifcfg script that exits in
Also in case it wasn't clear, I have ran "hwclock --systohc" after
"date" shows the correct time.
On Thu, Aug 9, 2012 at 3:30 PM, Russell Jones wrote:
> Craig,
>
> Let me clarify. I correct the time, and both "date" and "hwclock" both
> show the correct time. I reboot the server and "date" is a
CentOS Community,
Do you know how I can go about enabling system dumps and/or kernel core
dumps. I want to be able to have the system dump a core during a panic,
or crash.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listin
Russell Jones wrote:
> Also in case it wasn't clear, I have ran "hwclock --systohc" after
> "date" shows the correct time.
>
Please don't top post.
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
mark
>
>
> On Thu, Aug 9, 2012 at 3:30 PM, R
>
> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
> and see what the time is.
>
> mark
Thanks Mark. "hwclock" showed the right time before reboot. After
reboot, entering BIOS it still showed the correct local time. After
the server came up, "date" is slow by 5 ho
Russell Jones wrote:
>>
>> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
>> and see what the time is.
>>
>
> Thanks Mark. "hwclock" showed the right time before reboot. After
> reboot, entering BIOS it still showed the correct local time. After
> the server came up, "date
On Thu, Aug 9, 2012 at 4:30 PM, wrote:
> Russell Jones wrote:
>>>
>>> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
>>> and see what the time is.
>>>
>>
>> Thanks Mark. "hwclock" showed the right time before reboot. After
>> reboot, entering BIOS it still showed the cor
On 10/08/12 03:33, Richard Reina wrote:
> I have just installed 6.3 on a machine that was previously running
> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
> static IP as I intend to for this to be ma
on 8/9/2012 12:33 PM Russell Jones spake the following:
> Hi all,
>
> I am having an issue with some older CentOS 5.3 servers. Every time
> the server boots, it gives the error "Cannot access the hardware clock
> by any known method", and then promptly sets the time 5 hours behind
> the hardware c
On 10/08/12 04:31, Scott Robbins wrote:
...
> I tend to agree with the slashdot commentator who called it overcomplicated
> and unnecessary. It's another idea from
> Fedora, the theory, IIRC, was that this way, devices would always have the
> same name, whereas under the
> method that has been
Running CentOS 6.3
Areca hardware raid 10
fdisk -l
reports multiple partitions with the following description.
"Partition # does not end on cylinder boundary."
Disks are 512 byte sector size.
Raid stripe size is 64K.
but if I use
fdisk -lc
(-c Switch off DOS-compatible mode. )
I don't get
On Thu, 2012-08-09 at 15:35 -0700, Scott Silva wrote:
> on 8/9/2012 12:33 PM Russell Jones spake the following:
> > Hi all,
> >
> > I am having an issue with some older CentOS 5.3 servers. Every time
> > the server boots, it gives the error "Cannot access the hardware clock
> > by any known metho
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
>>
>> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
>> and see what the time is.
>>
>> mark
>
>
>
> Thanks Mark. "hwclock" showed the right time before reboot. After
> reboot, entering BIOS it still showed the c
On 08/09/2012 02:33 PM, Russell Jones wrote:
> Hi all,
>
> I am having an issue with some older CentOS 5.3 servers. Every time
> the server boots, it gives the error "Cannot access the hardware clock
> by any known method", and then promptly sets the time 5 hours behind
> the hardware clock, down t
On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
>
> On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
>
> >>
> >> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
> >> and see what the time is.
> >>
> >> mark
> >
> >
> >
> > Thanks Mark. "hwclock" sho
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck wrote:
> On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
>>
>> On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
>>
>> >>
>> >> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
>> >> and see what the time is.
>> >>
>> >>
On Thu, Aug 09, 2012 at 07:11:02PM -0500, Russell Jones wrote:
> On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck wrote:
>
> Thanks for the help!
>
> Dave: There are no options for time zones in the BIOS clock. The time
> is just "there" to be set. It is currently set to 7:08 PM, which is
> the current
On 10/08/12 09:18, Reindl Harald wrote:
> and that is why i use /etc/udev/rules.d/70-persistent-net.rules to
> pin device-name / MAC and no mac-address in ifconfig-scripts since
> many years
+1
Alternatively, with the biosdevname, you can pin the interface name to
the pci(e) slot. That way its a
40 matches
Mail list logo
