SL 5.7 + MRG
Hello! I installed a SL 5.7 x86_64 system and upgraded to latest packages with yum. Then I install kernel-rt from CERN MRG repository with adding repo files as recommended. I would like to play with MRG a bit. The kernel shipped with SL 5.7 is 2.6.18-274.17.1.el5 and the MRG kernel is 2.6.33.9-rt31.67.el5rt. When I use the system with kernel-rt the network on motherboard crashed after a while giving the following error message: Jan 30 16:50:08 lrtest kernel: [ cut here ] Jan 30 16:50:08 lrtest kernel: WARNING: at net/sched/sch_generic.c:259 dev_watchdog+0x11d/0x193() Jan 30 16:50:08 lrtest kernel: Hardware name: Jan 30 16:50:08 lrtest kernel: NETDEV WATCHDOG: eth0 (e100): transmit queue 0 timed out Jan 30 16:50:08 lrtest kernel: Modules linked in: oprofile autofs4 lm85 hwmon_vid hwmon hidp l2cap crc16 bluetooth rfkill lockd sunrpc dm_mirror dm_multipath scsi_dh video output sbs sbshc battery ac lp sg sr_mod cdrom skge e100 mii snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss serio_raw button parport_pc parport floppy snd_pcm snd_timer tpm_tis tpm tpm_bios snd i2c_i801 soundcore i2c_core snd_page_alloc pcspkr intel_agp shpchp iTCO_wdt iTCO_vendor_support dm_region_hash dm_log dm_mod pata_acpi ata_piix ata_generic libata sd_mod crc_t10dif scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: hwlat_detector] Jan 30 16:50:08 lrtest kernel: Pid: 5, comm: sirq-timer/0 Not tainted 2.6.33.9-rt31.67.el5rt #1 Jan 30 16:50:08 lrtest kernel: Call Trace: Jan 30 16:50:08 lrtest kernel: [812d0f04] ? dev_watchdog+0x11d/0x193 Jan 30 16:50:08 lrtest kernel: [8104233f] warn_slowpath_common+0x7c/0x94 Jan 30 16:50:08 lrtest kernel: [810423d6] warn_slowpath_fmt+0x69/0x6b Jan 30 16:50:08 lrtest kernel: [81032918] ? cpuacct_charge+0x5b/0x64 Jan 30 16:50:08 lrtest kernel: [813565bf] ? _raw_spin_unlock+0x28/0x33 Jan 30 16:50:08 lrtest kernel: [81356299] ? rt_spin_lock+0x15/0x17 Jan 30 16:50:08 lrtest kernel: [8135626b] ? rt_spin_unlock+0x15/0x17 Jan 30 16:50:08 lrtest kernel: [812d03e9] ? __netif_tx_unlock+0x1a/0x1c Jan 30 16:50:08 lrtest kernel: [812d0437] ? netif_tx_lock+0x4c/0x64 Jan 30 16:50:08 lrtest kernel: [812b956e] ? netdev_drivername+0x48/0x4f Jan 30 16:50:08 lrtest kernel: [812d0f04] dev_watchdog+0x11d/0x193 Jan 30 16:50:08 lrtest kernel: [8102f46a] ? need_resched+0x23/0x2d Jan 30 16:50:08 lrtest kernel: [81050966] run_timer_softirq+0x1e9/0x2c3 Jan 30 16:50:08 lrtest kernel: [812d0de7] ? dev_watchdog+0x0/0x193 Jan 30 16:50:08 lrtest kernel: [81048b18] run_ksoftirqd+0x17e/0x29e Jan 30 16:50:08 lrtest kernel: [8104899a] ? run_ksoftirqd+0x0/0x29e Jan 30 16:50:08 lrtest kernel: [8105daad] kthread+0x6e/0x76 Jan 30 16:50:08 lrtest kernel: [810373f8] ? finish_task_switch+0x62/0x81 Jan 30 16:50:08 lrtest kernel: [81003a94] kernel_thread_helper+0x4/0x10 Jan 30 16:50:08 lrtest kernel: [8105da3f] ? kthread+0x0/0x76 Jan 30 16:50:08 lrtest kernel: [81003a90] ? kernel_thread_helper+0x0/0x10 Jan 30 16:50:08 lrtest kernel: ---[ end trace 119d0fdfa1d74ba7 ]--- After error happens the system cannot access through terminal only from net (system has three cards). Looks like getty freeze or hang. When I try to shutdown/reboot the system it hangs at shutting down the interface eth0. The motherboard is an Intel D915GUX with latest BIOS EV91510A.86A.0482.2006.0222.2350. Now switch to non rt kernel hoping that will be fine. Anyone have similar experience? Any solution for this? Is it count that system is generic SL and the MRG kernel is CERN SL? Thanks, a
Re: serious bug in boot sequence when fsck is required
On Tue, Jan 31, 2012 at 2:28 AM, Sergio Ballestrero sergio.ballestr...@cern.ch wrote: On 30 Jan 2012, at 23:39, Yasha Karant wrote: Upon boot, automatic fsck failed, and a request was posted for root password. However, no more than one character of the password would be accepted, causing an endless loop to this condition and not allowing me control of the system (run fsck manually). For the next time (because there's always one ;-) ), you can use init=/bin/bash as a boot option, it will completely skip the standard init and therefore the root password request. It's anyway interesting that you could not login as root. What do you have in nsswitch and pam.d/system-auth ? Cheers, Sergio Usually works well, but bot if you've got your grub password protected. Such protection is common practice for high security setups, especially now that grub supports encrypted passwords. It's very advantageous for laptops, to prevent !@#$!@#$ smart alecks from booting your laptop into single user mode and throwing a party with your plain text stored data. (Subversion passwords and un-password-protected SSH keys come to mind, in particular. I've done this for workplace data recovery.) It also raises the threshold for root access to virtualization guests. I've had some fascinating discussions about system security for these, especially for LabManager setups where people could freely clone OS images and we *really* did not want our development users running rampant with root access. It's a very handy feature for slowing down people who should *not* have such automatic root access.
Re: serious bug in boot sequence when fsck is required
On 01/30/2012 11:28 PM, Sergio Ballestrero wrote: On 30 Jan 2012, at 23:39, Yasha Karant wrote: Upon boot, automatic fsck failed, and a request was posted for root password. However, no more than one character of the password would be accepted, causing an endless loop to this condition and not allowing me control of the system (run fsck manually). For the next time (because there's always one ;-) ), you can use init=/bin/bash as a boot option, it will completely skip the standard init and therefore the root password request. It's anyway interesting that you could not login as root. What do you have in nsswitch and pam.d/system-auth ? Cheers, Sergio It was not that I could not login as root. The prompt was there. However, instead of accepting the entire sequence of key presses (characters) that constitute the root password, after the first such character, whatever was running attempted to use the one character series as the password. This single character was not the correct password, the attempt was rejected, and the prompt for Control-D or root password was again presented as an endless loop. I will check both nsswitch and pam.d/system-auth when I get into the office. I do not like the idea of having an automatic root backdoor for security reasons (a university, in a department of computer science and engineering, with some bright CS, CE, and Physics majors -- some of whom do not accept in practice the ethics we attempt to instill). I have used and will continue to use the toor kludge as an alternative to root for situations in which the root home directory, etc., is corrupt -- but toor also is defended, not open. Thanks, Yasha
Re: Multiple Routes
On Jan 30, 2012, at 3:39 PM, Orion Poplawski wrote: You're sure your switch supports 802.3ad dynamic link aggregation? I had some switches that I thought did, but don't. what does dmesg | grep -Fi bond show? [root@tape ~]# dmesg | grep -Fi bond Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) bonding: bond0 is being created... bonding: cannot add bond bond0; already exists bonding: Bond creation failed. bonding: bond0: setting mode to 802.3ad (4). ADDRCONF(NETDEV_UP): bond0: link is not ready bonding: bond0: Adding slave eth2. bonding: bond0: Warning: failed to get speed and duplex from eth2, assumed to be 100Mb/sec and Full. bonding: bond0: Warning: Operation of 802.3ad mode requires ETHTOOL support in base driver for proper aggregator selection. bonding: bond0: enslaving eth2 as a backup interface with an up link. bonding: bond0: Adding slave eth3. bonding: bond0: Warning: failed to get speed and duplex from eth3, assumed to be 100Mb/sec and Full. bonding: bond0: Warning: Operation of 802.3ad mode requires ETHTOOL support in base driver for proper aggregator selection. bonding: bond0: enslaving eth3 as a backup interface with an up link. bonding: bond0: Adding slave eth4. bonding: bond0: Warning: failed to get speed and duplex from eth4, assumed to be 100Mb/sec and Full. bonding: bond0: Warning: Operation of 802.3ad mode requires ETHTOOL support in base driver for proper aggregator selection. bonding: bond0: enslaving eth4 as a backup interface with an up link. bonding: bond0: Adding slave eth5. bonding: bond0: Warning: failed to get speed and duplex from eth5, assumed to be 100Mb/sec and Full. bonding: bond0: Warning: Operation of 802.3ad mode requires ETHTOOL support in base driver for proper aggregator selection. bonding: bond0: enslaving eth5 as a backup interface with an up link. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bond0: no IPv6 routers present Also cat /proc/net/bonding/bond0 [root@tape ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Aggregator selection policy (ad_select): stable Active Aggregator Info: Aggregator ID: 1 Number of ports: 4 Actor Key: 17 Partner Key: 63257 Partner Mac Address: 00:15:77:e7:84:a2 Slave Interface: eth2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:a8 Aggregator ID: 1 Slave queue ID: 0 Slave Interface: eth3 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:a9 Aggregator ID: 1 Slave queue ID: 0 Slave Interface: eth4 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:ac Aggregator ID: 1 Slave queue ID: 0 Slave Interface: eth5 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:ad Aggregator ID: 1 Slave queue ID: 0 [root@tape ~]# ping 10.1.16.2 PING 10.1.16.2 (10.1.16.2) 56(84) bytes of data. From 10.1.16.20 icmp_seq=2 Destination Host Unreachable From 10.1.16.20 icmp_seq=3 Destination Host Unreachable From 10.1.16.20 icmp_seq=4 Destination Host Unreachable From 10.1.16.20 icmp_seq=6 Destination Host Unreachable From 10.1.16.20 icmp_seq=7 Destination Host Unreachable From 10.1.16.20 icmp_seq=8 Destination Host Unreachable ^C --- 10.1.16.2 ping statistics --- 9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8902ms pipe 3 [root@tape ~]# ethtool eth5 Settings for eth5: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: d Wake-on: d Current message level: 0x0003 (3) Link detected: yes See http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding Oddly enough if I move it to mode=0 I get a ping like this, but it's having a problem setting the ports speed and duplex. PING 10.1.16.2 (10.1.16.2) 56(84) bytes of data. 64 bytes from 10.1.16.2: icmp_seq=4 ttl=64 time=0.150 ms 64 bytes from 10.1.16.2: icmp_seq=8 ttl=64 time=0.191 ms 64 bytes from 10.1.16.2: icmp_seq=11 ttl=64 time=0.225 ms 64 bytes from 10.1.16.2: icmp_seq=15 ttl=64 time=0.278 ms 64 bytes from
Re: Multiple Routes
Thank you Orion Got enough information to noodle with it a bit more to check it all out! I ended up removing the trunk group from our Allied Telesys AT-9000/52 switch, turned off auto negotiation on the connected ports, and moved it to mode=balance-alb and miimon=100 (missed in config before). It's odd that it works for the other servers being trunked via 802.3ad, but I think the problem comes in that the switch only supports 12 LACP groups and we probably hit that barrier by trying to add this server. Investigating further…. So here's what my config looks like now…. [root@tape ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 IPADDR=10.1.16.20 NETWORK=10.1.16.0 NETMASK=255.255.224.0 GATEWAY= ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS=mode=6 miimon=100 [root@tape ~]# cat /etc/sysconfig/network-scripts/route-bond0 default via 172.16.0.1 dev eth0 10.1.0.0/19 via 10.1.16.20 dev bond0 And logs are reporting back….. [root@tape ~]# dmesg | grep -Fi bond Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) bonding: bond0 is being created... bonding: cannot add bond bond0; already exists bonding: Bond creation failed. bonding: bond0: setting mode to balance-alb (6). bonding: bond0: Setting MII monitoring interval to 100. ADDRCONF(NETDEV_UP): bond0: link is not ready bonding: bond0: Adding slave eth2. bonding: bond0: enslaving eth2 as an active interface with a down link. bonding: bond0: Adding slave eth3. bonding: bond0: enslaving eth3 as an active interface with a down link. bonding: bond0: Adding slave eth4. bonding: bond0: enslaving eth4 as an active interface with a down link. bonding: bond0: Adding slave eth5. bonding: bond0: enslaving eth5 as an active interface with a down link. bond0: link status definitely up for interface eth2, 1000 Mbps full duplex. bonding: bond0: making interface eth2 the new active one. bonding: bond0: first active interface up! bond0: link status definitely up for interface eth3, 1000 Mbps full duplex. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bond0: link status definitely up for interface eth4, 1000 Mbps full duplex. bond0: link status definitely up for interface eth5, 1000 Mbps full duplex. bond0: no IPv6 routers present [root@tape ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: adaptive load balancing Primary Slave: None Currently Active Slave: eth2 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:a8 Slave queue ID: 0 Slave Interface: eth3 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:a9 Slave queue ID: 0 Slave Interface: eth4 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:ac Slave queue ID: 0 Slave Interface: eth5 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:1b:21:21:2f:ad Slave queue ID: 0
Adobe Reader 9 + 64 bit SL6...?
Hello all, I've been trying to get Adobe Reader 9 working on a machine I take care of, and it won't run when not run by root. I have installed the adobe-release repo, and installed adobe reader with yum install AdobeReader_enu Users log into this machine and their home directory is mounted over NFS. The machine is 64 bit Scientific Linux release 6.0 (Carbon) $ yum info AdobeReader_enu Loaded plugins: refresh-packagekit Available Packages Name : AdobeReader_enu Arch : i486 Version: 9.4.6 Release: 1 Size : 57 M Repo : adobe-linux-i386 Summary: Adobe Reader, an application to easily view, print and collaborate on PDF files. URL: http://www.adobe.com License: Commercial Description: Adobe Reader software is the global standard for electronic document sharing. It is the only PDF file viewer that can open and interact with all PDF documents. Use Adobe Reader to view, search, : digitally sign, verify, print, and collaborate on Adobe PDF files. (this the yum info is after having uninstalled the application, which is why it shows the repo as adobe-linux-i386 and not installed When I run acroread as root, Adobe Reader starts up fine. When I run acroread as any other user (all other users use an NFS mounted home directory) Reader won't start. Doing an strace shows that the reader hits a segfault when run as any user other than root - and I can't tell why it's segfaulting. The strace doesn't actually tell me anything interesting beyond that, other than the fact that reader stats the local directory several times. I've managed to coax a crash log from adobe reader, but I get some simple list that doesn't tell me much of anything: == /usr/bin/acroread [0x8508e25] [@0x8048000] (__kernel_sigreturn+0x0) [0x110400] [@0x11] /usr/bin/acroread [0x850c0ac] [@0x8048000] /usr/bin/acroread(main+0x87) [0x85705c5] [@0x8048000] /lib/libc.so.6(__libc_start_main+0xe6) [0x3e07ce6] [@0x3df1000] == Looking at the acroread command itself, it appears to be a complex script which then bootloads a bunch of library files and then loads reader from another directory. I've attempted to recreate this script minimally by setting the LD_LIBRARY_PATH as set in the script and then run the binary, but it then proceeds to complain at me that I am not starting it up via the script. Bananas, I tell you! Well, I spent the better part of an hour attempting to get it working, and will continue to attempt to get it working, but has anyone experienced this before? perhaps someone can shed some light on my predicament? Maybe an update to 6.1 is in order? Thanks! Christopher Tooley ctoo...@uvic.ca Systems, HEP/Astronomy UVic
Re: Adobe Reader 9 + 64 bit SL6...?
On Tue, Jan 31, 2012 at 12:29 PM, Christopher Tooley ctoo...@uvic.ca wrote: Hello all, I've been trying to get Adobe Reader 9 working on a machine I take care of, and it won't run when not run by root. I've found that under certain circumstances Adobe Reader 9 requires that nscd be running. I'm not certain why. In my setup user accounts are via LDAP, and I'd assumed that was the issue, but it may go further. I'd suggest starting nscd and seeing if that fixes it. Jeff Anderson Lawrence Berkeley National Lab I have installed the adobe-release repo, and installed adobe reader with yum install AdobeReader_enu Users log into this machine and their home directory is mounted over NFS. The machine is 64 bit Scientific Linux release 6.0 (Carbon) $ yum info AdobeReader_enu Loaded plugins: refresh-packagekit Available Packages Name : AdobeReader_enu Arch : i486 Version : 9.4.6 Release : 1 Size : 57 M Repo : adobe-linux-i386 Summary : Adobe Reader, an application to easily view, print and collaborate on PDF files. URL : http://www.adobe.com License : Commercial Description: Adobe Reader software is the global standard for electronic document sharing. It is the only PDF file viewer that can open and interact with all PDF documents. Use Adobe Reader to view, search, : digitally sign, verify, print, and collaborate on Adobe PDF files. (this the yum info is after having uninstalled the application, which is why it shows the repo as adobe-linux-i386 and not installed When I run acroread as root, Adobe Reader starts up fine. When I run acroread as any other user (all other users use an NFS mounted home directory) Reader won't start. Doing an strace shows that the reader hits a segfault when run as any user other than root - and I can't tell why it's segfaulting. The strace doesn't actually tell me anything interesting beyond that, other than the fact that reader stats the local directory several times. I've managed to coax a crash log from adobe reader, but I get some simple list that doesn't tell me much of anything: == /usr/bin/acroread [0x8508e25] [@0x8048000] (__kernel_sigreturn+0x0) [0x110400] [@0x11] /usr/bin/acroread [0x850c0ac] [@0x8048000] /usr/bin/acroread(main+0x87) [0x85705c5] [@0x8048000] /lib/libc.so.6(__libc_start_main+0xe6) [0x3e07ce6] [@0x3df1000] == Looking at the acroread command itself, it appears to be a complex script which then bootloads a bunch of library files and then loads reader from another directory. I've attempted to recreate this script minimally by setting the LD_LIBRARY_PATH as set in the script and then run the binary, but it then proceeds to complain at me that I am not starting it up via the script. Bananas, I tell you! Well, I spent the better part of an hour attempting to get it working, and will continue to attempt to get it working, but has anyone experienced this before? perhaps someone can shed some light on my predicament? Maybe an update to 6.1 is in order? Thanks! Christopher Tooley ctoo...@uvic.ca Systems, HEP/Astronomy UVic -- -- Jeffrey Anderson | jdander...@lbl.gov Lawrence Berkeley National Laboratory | Office: 50A-5104E | Mailstop 50A-5101 Phone: 510 486-4208 | Fax: 510 486-4204
Re: serious bug in boot sequence when fsck is required
On 31 Jan 2012, at 16:59, Yasha Karant wrote: On 01/30/2012 11:28 PM, Sergio Ballestrero wrote: For the next time (because there's always one ;-) ), you can use init=/bin/bash as a boot option, it will completely skip the standard init and therefore the root password request. I do not like the idea of having an automatic root backdoor for security reasons (a university, in a department of computer science and engineering, with some bright CS, CE, and Physics majors -- some of whom do not accept in practice the ethics we attempt to instill). I have used and will continue to use the toor kludge as an alternative to root for situations in which the root home directory, etc., is corrupt -- but toor also is defended, not open. the init= backdoor is there in the kernel, whether you like having it or not (unless you patch it away) : http://lxr.free-electrons.com/source/init/main.c#L757 so, as Niko was saying, you anyway must have a Grub password on any system that you care a bit about, it's the only defence. And, I would add, BIOS settings password. And a big locked cage around it, etc etc ;-) Cheers, Sergio -- Sergio Ballestrero - http://physics.uj.ac.za/psiwiki/Ballestrero University of Johannesburg, Physics Department ATLAS TDAQ sysadmin group
[rhelv6-list] Announcement: Red Hat Enterprise Linux Life Cycle Extended to Ten Years (fwd)
FYI -- Forwarded message -- Date: Tue, 31 Jan 2012 12:20:13 -0500 From: Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list rhelv6-l...@redhat.com To: rhelv6-l...@redhat.com Subject: [rhelv6-list] Announcement: Red Hat Enterprise Linux Life Cycle Extended to Ten Years Today Red Hat is pleased to announce that it has extended the life cycle of Red Hat Enterprise Linux 5, 6 and future releases from seven to 10 years, effective immediately. This announcement is in response to the widespread adoption of Red Hat Enterprise Linux 5 since its introduction in 2007, and the increasing rate of adoption of Red Hat Enterprise Linux 6 since its launch in 2010. During the life cycle of Red Hat Enterprise Linux, customers take advantage of a multitude of benefits, including feature enhancements, critical bug and security fixes, as well as award-winning support from Red Hat’s Global Support Services team. Customers also enjoy stability from Red Hat Enterprise Linux resulting from Red Hat's commitment to ABI and API compatibility during the life cycle. Finally, Red Hat delivers a steady stream of supported hardware platforms, aligning to the new introduction cycles of hardware OEM partners. The result of the extended life cycle is that customers will enjoy all of the benefits of their subscription over a longer period of time. Specifically, this means additional time to take advantage of the significant investments that customers make in Red Hat Enterprise Linux related to their business critical applications. Enterprise customers will now have more options for their Red Hat Enterprise Linux implementations, and can use the longer life cycle to plan for migrations as well as new deployments. We are excited about this announcement, and in particular about the additional value that it provides to customers, in response to their reliance on Red Hat to help run and grow their business. For additional details, please refer to the following resources: - The press release associated with this announcement: http://www.redhat.com/about/news/press-archive/2012/1/red-hat-enterprise-linux-stability-drives-demand-for-more-flexibility-in-long-term-operating-system-deployments - The Red Hat Enterprise Linux life cycle web page: https://access.redhat.com/support/policy/updates/errata/ - An FAQ on the Red Hat Customer Portal: https://access.redhat.com/kb/docs/DOC-69647 Please consult your primary Red Hat contact to understand more detail regarding this exciting announcement. ___ rhelv6-list mailing list rhelv6-l...@redhat.com https://www.redhat.com/mailman/listinfo/rhelv6-list
Re: Adobe Reader 9 + 64 bit SL6...?
I've found that under certain circumstances Adobe Reader 9 requires that nscd be running. I'm not certain why. In my setup user accounts are via LDAP, and I'd assumed that was the issue, but it may go further. I'd suggest starting nscd and seeing if that fixes it. That did it! Started nscd, reinstalled AdobeReader_enu and now it works. What a bizarre solution. Thank you so much for the help! Christopher Tooley ctoo...@uvic.ca Systems, HEP/Astronomy UVic
Re: serious bug in boot sequence when fsck is required
Hi, If you add RD_NO_PLYMOUTH kernel boot option, you will be able to enter single user password. Regards, Geoffroy On Tue, 31 Jan 2012 07:59:10 -0800, Yasha Karant ykar...@csusb.edu wrote: On 01/30/2012 11:28 PM, Sergio Ballestrero wrote: On 30 Jan 2012, at 23:39, Yasha Karant wrote: Upon boot, automatic fsck failed, and a request was posted for root password. However, no more than one character of the password would be accepted, causing an endless loop to this condition and not allowing me control of the system (run fsck manually). For the next time (because there's always one ;-) ), you can use init=/bin/bash as a boot option, it will completely skip the standard init and therefore the root password request. It's anyway interesting that you could not login as root. What do you have in nsswitch and pam.d/system-auth ? Cheers, Sergio It was not that I could not login as root. The prompt was there. However, instead of accepting the entire sequence of key presses (characters) that constitute the root password, after the first such character, whatever was running attempted to use the one character series as the password. This single character was not the correct password, the attempt was rejected, and the prompt for Control-D or root password was again presented as an endless loop. I will check both nsswitch and pam.d/system-auth when I get into the office. I do not like the idea of having an automatic root backdoor for security reasons (a university, in a department of computer science and engineering, with some bright CS, CE, and Physics majors -- some of whom do not accept in practice the ethics we attempt to instill). I have used and will continue to use the toor kludge as an alternative to root for situations in which the root home directory, etc., is corrupt -- but toor also is defended, not open. Thanks, Yasha =
Re: serious bug in boot sequence when fsck is required
rd_NO_PLYMOUTH On Wed, 1 Feb 2012 01:32:53 -0600, Geoffroy Turtaut geoffroy.turt...@dassault-aviation.com wrote: Hi, If you add RD_NO_PLYMOUTH kernel boot option, you will be able to enter single user password. Regards, Geoffroy
