CentOS Errata and Bugfix Advisory 2012:1155
Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1155.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
Una gran ayuda por favor
Estoy instalando moodle pero al confirmar las rutas
pe parece el mesaje de que El directorio de datos (/var/www/moodledata) no
puede ser creada por el instalador
pero si tengo creada la carpeta moodledata
no ce que hacer
le agradezco su gran ayuda!!
-Mensaje
Comprobaste los permisos de la carpeta? Y a quién pertenece dicha carpeta?
Realiza un chown -R apache:apache /var/www (suponiendo que el usuario del
servicio Web sea apache, en el grupo apache), y por si acaso, podrías
probar con un chmod a+rw (para que todos los usuarios puedan leer y
escribir,
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 there is
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 mentioned
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 there is
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 sudoers
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
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 to set
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
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 intend
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 ethernet a
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 m.r...@5-cent.us:
Scott Robbins 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.
After the system is up. hwclock works
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
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 fedora
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, m.r...@5-cent.us wrote:
Russell Jones wrote:
Hi all,
I am having an issue with some older CentOS 5.3
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, down
On Thu, Aug 9, 2012 at 1:47 PM, m.r...@5-cent.us 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
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 craig.wh...@ttiltd.com wrote:
until you set your clock so that 'date' gives the right time, don't
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 arjone...@gmail.com wrote:
Craig,
Let me clarify. I correct the time, and both date and hwclock both
show the correct time. I reboot the server and
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
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, Russell
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 hours.
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 is slow by 5
On Thu, Aug 9, 2012 at 4:30 PM, m.r...@5-cent.us 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 correct
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
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 clock,
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 used
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 method, and then
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 correct local
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 to the
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 showed the right time before
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck mar...@pennswoods.net 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 mar...@pennswoods.net 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
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
42 matches
Mail list logo
