[CentOS] CentOS 7 Gnome
I installed CentOS 7 from the DVD iso file: CentOS-7-x86_64-DVD-1503-01.iso Yum update was used (with no update issues) to install and update many packages. The installer is significantly different from CentOS 6 where one can basicallychoose to "install everything" if one has the patience to check all productsand all software options within those categories. During the CentOS 7 install,the "Development Workstation" was selected with all options checked. The new gnome Desktop menu bar still has Applications and Places, but the Systemmenu is gone. I even tried installing the minimal CentOS 7 system and then addingthe gnome, but that yielded the same result, still no System menu item on the bar. One interesting fact is that the RH admin guide actually refers to the System menu and other items on the menu bar but some of them are actually absent. Red_Hat_Enterprise_Linux-7-Desktop_Migration_and_Administration_Guide-en-US.pdf Can anyone provide assistance in getting the system menu back in gnome. Thanks ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] sudoers
My experience with RHEL and CentOS is quite limited, andwould classify me as novice. I have been running CentOS 6for a little over a year and recently brought up a CentOS 7system as a virtual machine under Windows 7. One of the first things I usually do after installation isedit the /etc/sudoers file using visudo to give a specificuser or specific users privileges as indicated in the fileexcerpt below. The visudo editor issued no error messageswhen creating the line for sarah. ## user MACHINE=COMMANDS ## ## The COMMANDS section may have other options added to it. ## ## Allow root to run any commands anywhere root ALL=(ALL) ALL sarahALL=(ALL) NOPASSWD: ALL On our CentOS 6 systems, the NOPASSWD option works as itis intended to work. No password prompt is presented for commands such as "sudo cat /etc/sudoers". On CentOS 7,the NOPASSWD option does not seem to work, and a promptfor sarah's password is always issued. Can someone help solve this CentOS 7 mystery? Thank you and best regards. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] IPMI/BMC/BIOS
We have recently been asked to evaluate some computing machinery for a new project. This particular end user has very limited experience with the stated security requirements in a lights-out environment. Their primary work (as well as mine) in the past has been with very small, simple networks of desktop machines and a few servers with extremely limited access. For the most part, their admins haverefused to use any maintenance connectivity to servers other thanthe primary serial ports. There is a concern about system security primarily driven by recent information searches performed by end user admins and included below. IPMI/BMC Security Issues https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface http://www.google.com Search: IPMI "Security Holes" -- Hits: 14,500 http://www.google.com Search: IPMI BMC "Security Holes" -- Hits: 4950 BIOS Security Issues https://en.wikipedia.org/wiki/BIOS http://www.google.com Search: BIOS "Security Holes" -- Hits: 342,000 My initial recommendation was to use a totally separate network for any service processors within the servers that implement IPMI/BMC capabilities. This has been standard practice in most systems I have worked on in the past, and has allowed certification with essentially no problems. The BIOS concern seems to be another issue to be addressed separately. Any connectivity and access to a system brings security issues. The list from these searches is huge. Are there specific things that must always be addressed for system security besides keeping junior admins off the server supporting the maintenance network? Thanks in advance for any feedback and best regards. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] USB Connected Voice Recorders
We plan to use new digital voice recorders. Products are available from Olympus, Sony, and others. All of these digital voice recorders offer file-based audio storage. We would like to take advantage of this feature and move the files to our computers. It is not clear whether there is a difference in the product features described as "USB connection" and "USB direct connection." Is this difference in USB connectivity a concern for file transfer to CentOS computers? Thanks in advance for any information. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Serial Communication
Many years ago, we began scrapping the RTOS approach for some of our timing-critical applications. Our first applications were based on Solaris real-time extensions and served well us well for many years. Then came the era of shaky support for Intel Solaris and we moved many applications to Linux. There appeared to be no actual need for special real-time features with a good Linux distribution kernel and a GHz processors. One of our most productive applications involves special test equipment computers that drive high speed serial ports. The original development of these systems had the "added benefit" of helping us to learn udev rules. The serial communication is very flexible and most of it is script driven. A current need to update computing platforms is driving script review. There appears to be a bit of variety in outputs to the serial drivers. The echo of a string with redirection to the serial driver, cat of a file with redirection to the serial driver and dd of=/dev/ are methods used at various places in the scripts. It is not at all clear what drove the choice of the output method at various points in the application. In addition, changing the method of output has not succeeded in breaking most of the applications. Is there some fundamental difference between these methods of output to the driver that might trip us up as we simplify the scripts and port to new computer platforms? Thanks in advance for any assistance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Power Management
Recent power management discussions plugged into one of our current frustrations, namely the interaction of the screen lock and power-save features on Intel/CentOS 6 platforms. We certainly would not have guessed that locking the screen would inhibit going into the power-save mode, but it sure seems to do exactly that on some of our test platforms. If one leaves the desktop idle for the timeout period, the computer sleeps. If one locks the screen and then leaves the machine idle, the computer does not sleep. We were hoping that this "feature" was isolated to just our older Dell desktop machine hardware and firmware, but it appears elsewhere as well. Possibly more interesting is that most of our systems were loaded with CentOS 6.X almost two years ago and have been updated at least weekly ever since. This new power-save scenario has appeared just within the last three weeks,and our investigations have not discovered the cause ora solution. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] HP OfficeJet Printing
There has been a bit of grumbling recently about HP printer capability in one of our smallest prototyping Labs. We have a single GigE switch connecting a Windows 7 machine and a Dell/CentOS-6 machine. The CentOS machine also has connectivity via another network. Currently, only the Windows 7 machine has been setup for printing on our HP OfficeJet 8615. Our Samba effort on the CentOS system has not been successful so we use Cygwin and ftp to move files to the Windows 7 system for printing. Being able to print directly from the CentOS 6 system would be most convenient. Software supporting the HP OfficeJet Pro 8615 is apparently available as indicated in the links and other information below. We also see that hplip was apparently part of an installation or update performed on the CentOS 6 Dell machine at some point in time. http://sourceforge.net/projects/hplip/?source=typ_redirect http://hplipopensource.com/hplip-web/index.html The current version of the HPLIP solution is: 3.15.11. [user@dell ~]$ uname -a Linux dell 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 2015\ x86_64 x86_64 x86_64 GNU/Linux [user@dell ~]$ [user@dell ~]$ rpm -qa hplip hplip-3.14.6-3.el6.x86_64 [user@dell ~]$ [user@dell ~]$ which hp-setup /usr/bin/hp-setup Using this open source software seems easy enough, but we have concerns about printing from the Windows 7 machine if the CentOS 6 system is setup for printing. Is there any significant possibility that printer setup or printer use on the CentOS 6 system will negatively impact printing functionality on the Windows 7 machine? Thanks in advance for any help or advice, and Happy New Year. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] HP OfficeJet Printing
I now understand that one piece of important informationwas left out of my original posting. The printer is alreadyconnected to the same network as the Window 7 and the CentOScomputers. Current access from the Windows 7 machine is viathe network supported by the GigE switch. On Saturday, January 2, 2016 4:21 AM, Nux! wrote: Why go through all this trouble when you can connect the printer to the network directly and be done with it? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Chris Olson" > To: "CentOS Mailing List" > Sent: Friday, 1 January, 2016 16:29:17 > Subject: [CentOS] HP OfficeJet Printing > There has been a bit of grumbling recently about HP printer capability > in one of our smallest prototyping Labs. We have a single GigE switch > connecting a Windows 7 machine and a Dell/CentOS-6 machine. The CentOS > machine also has connectivity via another network. Currently, only the > Windows 7 machine has been setup for printing on our HP OfficeJet 8615. > Our Samba effort on the CentOS system has not been successful so we use > Cygwin and ftp to move files to the Windows 7 system for printing. Being > able to print directly from the CentOS 6 system would be most convenient. > > Software supporting the HP OfficeJet Pro 8615 is apparently available > as indicated in the links and other information below. We also see > that hplip was apparently part of an installation or update performed > on the CentOS 6 Dell machine at some point in time. > > http://sourceforge.net/projects/hplip/?source=typ_redirect > http://hplipopensource.com/hplip-web/index.html > The current version of the HPLIP solution is: 3.15.11. > > [user@dell ~]$ uname -a > Linux dell 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 2015\ > x86_64 x86_64 x86_64 GNU/Linux > [user@dell ~]$ > [user@dell ~]$ rpm -qa hplip > hplip-3.14.6-3.el6.x86_64 > [user@dell ~]$ > [user@dell ~]$ which hp-setup > > /usr/bin/hp-setup > > Using this open source software seems easy enough, but we have concerns > about printing from the Windows 7 machine if the CentOS 6 system is setup > for printing. > > Is there any significant possibility that printer setup or printer use > on the CentOS 6 system will negatively impact printing functionality > on the Windows 7 machine? > > Thanks in advance for any help or advice, and Happy New Year. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Pi 2 Alternatives
We have a requirement for a new application that will be used fixed, portable, and mobile. The hardware requirements drive the need for networking as well as some general purpose and special purpose interfaces. The software requirements are quite simple in comparison to many of our much larger systems with similar hardware requirements. We are not significantly restricted in choice of storage peripherals or other devices that may be needed. We believe that a small, single board computer will meet all requirements as long as it can run Linux. We have identified the need for approximately six prototyping units to support the initial production of about 200 to 300 operational systems. Our development and deployment time frame does not drive the need for an extremely rapid product decision, and there are pre-planned upgrade cycles over the next five years. An internal group has achieved a significant head of steam in support of using the Pi 2 Model B. The support enthusiasm may be partly technical and partly the hype associated with jumping into the Pi community. The number of suppliers does appear to support our supply chain and sustainment requirements, however the Linux available for the Pi 2 does not appear to be optimal. It would be better if there were choices that include a standard Linux distribution such as CentOS. This certainly seems like one of those situations where a trade of single board computer products is appropriate and achievable. There are products similar to the Pi 2 capable of running a more standard Linux distribution that we might consider. Does anyone have an experience-based single board computer recommendation? Thanks in advance for any product recommendations. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Nearly Instant Karma
Our smallest network has just three systems permanently attached to a 100/1000 router. There is one additional port available to temporarily plug in a laptop. The largest systems are both Dells, one running Windows 7 and one running CentOS 6.7. The Windows 7 system supports three flavors of Linux as virtual machines. The CentOS system is often used for data file import from USB-attached devices such as cell phones, charging batteries in the USB-attached devices, and for access to external email accounts. The CentOS system was in power save mode when I plugged in a Samsung cell phone for charging and extraction of several photo files. I then moved to the Windows 7 system to do some "paper work" on a web site that is known to require the use of IE for browser access. While on the Windows 7 system I did a quick email check and responded to one of our contacts at a remote site. He was having "difficulty" with file from an external site downloaded on his Windows 7 system. I took the opportunity in my email reply to comment on the great safety and stability of Linux systems. After about two hours I returned to the CentOS 6.7 system to check on the charging status and move the photo files. Yellow lights were showing on both computer and monitor. The system display, and the optical mouse would not return to normal operation as they usually do with a quick push on the front power button. The power button light did turn green and I was able to log in via ssh from a Cygwin shell on the Windows 7 system. It took two reboots executed remotely to bring back full display and mouse functionality. I believe that this was the first time anyone has plugged in a USB device into the CentOS 6.7 system while it is in power save mode.We now have a warning tag hanging over the USB ports on the system. Is there some characteristic of CentOS systems that we should have known about that could have caused this problem? Does Yahoo web mail have an easy way to retract my gloating email? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System Time Source
One of our STEM interns recently observed that there are inexpensive clocks that sync via radio to standard time services. This begged a question about why every computer would not have a radio module to receive time. Our senior staff did not have a good answer or if time from such a radio module would be supported by the operating system. When I was a student, such questions would have earned me extra homework assignments. We now have only PC directed relationships with interns so we don't assign any extra homework for curiosity. Can anyone help with the answers? Thanks and best regards. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System Time Source Responses
It looks like we may have hit on a popular subject with the questions about system time sources. Thanks for all of the responses. Our intern and senior software staff now have useful information and new perspective. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System Start-Up Issue
We run several Intel-based CentOS machines. They are all at 6.9 or 7.x. One of each OS is Oracle VirtualBox hosted on an up to date Windows 7 system. We use these virtual machines for checkout of new applications before they are loaded on native CentOS platforms. Regular weekly updates are run on all of our CentOS machines. I went on vacation right after an update to one of our virtual CentOS 6.9 systems so it was not restarted for a period of time. Now it will not complete boot-up with the gnome display never fully launched. A progress bar at the bottom of the start-up screen never reaches completion. We have not been able to detect a running system on the network. Two options for stopping the CentOS 6.9 virtual machine have been tried. One is to "power off" and the other is to "send the shutdown message". Both of these options appear to work properly. The shutdown output scrolls by very fast but it looks reasonable and the virtual machine eventually closes. We have also tried suspending boot-up and selecting two previous working kernels. This yields the same result of an incomplete start up. Shutdown of these old kernel systems appears the same as shutdown of the newest kernel. However, we have not been able to determine from any of the shutdown sequences exactly how much of the system was actually running. Having very little experience with such start-up issues, we are at a loss to determine how to salvage the CentOS 6.9 virtual machine. Is there a standard way to start up a system without any extras like gnome to see if we can get a running system? Would it be wise to attempt using yum update after we get a running system to see if issues are corrected? Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] System Start-Up Issue
None of the previous kernels will boot properly. On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us" wrote: Chris Olson wrote: > I went on vacation right after an update to one of our virtual CentOS 6.9 > systems so it was not restarted for a period of time. Now it will not > complete boot-up with the gnome display never fully launched. A progress > bar at the bottom of the start-up screen never reaches completion. We have > not been able to detect a running system on the network. > > Two options for stopping the CentOS 6.9 virtual machine have been tried. > One is to "power off" and the other is to "send the shutdown message". > Both of these options appear to work properly. The shutdown output Suggestion: boot to the previous kernel. If that works, reinstall the update, then reboot to it. We had real issues months back, where a yum-cron appeared to half-ignore the exclude=kernel line in yum.conf, and it would consistently fail to boot, but once the above was done, reinstalling the latest kernel, *then* it rebooted with no problem. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System Start-Up Issue Progress
My thanks to all that responded to my posting about our virtual machine CentOS 6 system start-up issue. I found the alternative boot options to be the most helpful. Interrupting the boot-up process with Alt-d or Escape allowed me to see what appears to be a quite normal string of start, install and mount activity. However, this process ends with the system hanging at the point below: Starting ipmidetectd: ipmidetectd: No nodes configured [FAILED] Starting sendmail: It is not clear to me whether the boot-up process is hanging due to the failed starting of ipmidetectd or sendmail, but I suspect that the ipmidetectd start up failure is the actual cause. It is not clear whether any IPMI related features were ever installed. Interrupting the boot-up process and selecting Run Level 1 results in a functioning system. Starting with other Run Levels results in the incomplete boot-up process noted previously. Using the "service network start" command yielded functional network and internet connectivity. This enabled the successful execution of yum update. The update consisted of kernel and other updates with a total download size of 274 MB. After this update, the boot-up process still hangs at the point indicated above. Why this is happening is still a mystery and if it actually is IPMI related, why would this be appropriate or even needed in a CentOS system that is running on VirualBox. There is no IPMI related hardware accessible to the virtual CentOS system or on the Windows 7 host system. It would be good if the IPMI start-up could be disabled. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] System Start-Up Issue Progress
Once again, my thanks to all that responded to my posting about our virtual machine CentOS 6 system start-up issue. Addressing sendmail was the key to the start-up issue. While operating at Run Level 1, chkconfig sendmail off was commanded followed by the reboot command. This brought up the system with the complete and operational GUI interface. The maillog had several entries from the past few days. Possibly the most telling of these messages are included below: computer sendmail[]: unable to qualify my own domain name (computer) computer sendmail[]: My unqualified host name (computer) unknown; sleeping for retry During the days that we were attempting to troubleshoot the problem, the boot-up process was left on one occasion for about one hour. It appears that the sleeping for retry may have been inspired by that famous gentleman R.V. Winkle. Since we do not need sendmail on this system, we will just leave it turned off along with IPMI features. It remains a mystery what could have happened during a standard yum update of the system to cause this domain and/or host related sendmail issue. On Tuesday, July 4, 2017 7:14 AM, Jonathan Billings wrote: On Jul 4, 2017, at 8:01 AM, Chris Olson wrote: > Starting ipmidetectd: ipmidetectd: No nodes configured [FAILED] > Starting sendmail: Any chance that this system doesn’t have valid DNS lookups? What I see above is that ipmidetetd failed (which doesn’t block) and then it is stuck starting sendmail. If memory serves me (I haven’t used sendmail in years) sendmail gets stuck waiting for a response from DNS servers when it’s performing part of its startup. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] System Start-Up Issue Progress
Organization policy dictates that information copied from systems with Internet access be "sanitized". Thus the FAKE name computer as well as the designations and provided in my previous messages and presented again below: computer sendmail[]: unable to qualify my own domain name (computer) computer sendmail[]: My unqualified host name (computer) unknown; sleeping for retry The actual system has totally legitimate names for domain and host. What actually happened during the system update is still being investigated. In the three years that this virtual CentOS 6 system has been running, updates have taken us from 6.5 to 6.9. These updates have been executed using yum update and accepting all updates available. This is the very first time anything like this has happened. All updates have been successful. It is very fortunate that we do not need sendmail. Thanks again for responses to my messages. We are still learning. On Tuesday, July 4, 2017 1:42 PM, Alexander Dalloz wrote: Am 04.07.2017 um 19:13 schrieb Gordon Messmer: > On 07/04/2017 09:21 AM, Chris Olson wrote: >> It remains a mystery what could have happened during a standard yum >> update of the system to cause this domain and/or host related sendmail >> issue. > > > Run "hostname". Has the hostname changed? Run "ls -l /etc/hosts > /etc/resolv.conf". Have those files changed recently? > > It's possible that this system was working in the past because its > hostname was set up in DNS, and was removed. In that case, the problem > wasn't related to "yum." sendmail would (IIRC) continue working after > the system's hostname was removed from DNS, until the next time the > system rebooted. Sendmail demands a hostname with at least a single dot in it. "computer" is in no way a valid FQDN. "computer.localdomain" would be fine and if it has an entry in /etc/hosts. Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS SDR Support
Several weeks ago, we posted a message seeking information about time sources. There were many helpful and educational responses. An excerpt from one of the responses is included below. We have been following up with regard to how SDR capabilities might be used for obtaining time using SDR dongles as well as using the time source product referenced in that response. Our SDR investigation has yielded many sources of information, but not a source dedicated to CentOS support for SDR products. Is there a CentOS subgroup and mail list directly involved with SDR device or system support? The SDR information resulting from our search has many references to ADS-B and the P3. It is almost like one absolutely must have a P3 to make use of SDR products. One thing that we did not find was any reference at all to SDR products and software for monitoring the frequencies used by recreational Remote Controlled Aircraft. Thanks again for all the helpful system time responses. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS SDR Support
Software Defined Radio On Wednesday, July 19, 2017 8:40 AM, "m.r...@5-cent.us" wrote: Chris Olson wrote: > > Several weeks ago, we posted a message seeking information about > time sources. There were many helpful and educational responses. > An excerpt from one of the responses is included below. We have > been following up with regard to how SDR capabilities might be > used for obtaining time using SDR dongles as well as using the > time source product referenced in that response. I missed that one, so a clarification, please: is that software-defined-radio, or the SDR that ipmitool offers info on, or mark -- The great thing about standards is that there are so many of them ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Power Fail Protection
Some of our largest systems run Windows because it supports engineering applications that we use regularly. These applications have unattended runs that often take between ten and fifteen hours to complete. We have taken the recommendation of the application supplier and equipped these Windows machines with UPS protection for 30 minutes at full load. The UPSs are Ethernet connected. A support application on the Windows engineering machine communicates with the UPS to detect and address any facility power failure. The long run engineering application is then suspended at a restart point and the system is shut down. We initiate job completion manually from the suspension restart point after the system has reliable power and is rebooted. If we wanted to protect our CentOS systems from facility power failure in a similar way, is there operating system or other standard support that we might employ? Most of the Linux-based applications are not as critical as the engineering applications on the Windows machines. There is a significant amount of processor idle time on several of the CentOS systems during non-work hours when the systems are unattended. Several CentOS systems are supported currently with UPSs, but they run out and the system loses power if it is unattended. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Power Fail Protection Update
Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected. Most of these machines are desktop/deskside machines that are likely to be idle during non-work hours. It is also likely that they will be hibernating or in a power save mode. In the power save mode, these machines do not respond to keyboard or mouse activity. They also do not respond to network traffic such as a ping from other systems on the network. The method we use to wake them up is a quick push on the power button when the hibernation state is indicated by the button's yellow LED display. This state of hibernation leaves us wondering if these systems will be able to respond to network messages sent by the UPS. We have not yet made it all the way through the NUT and UPS documentation. The hibernation answer may very well be therein, but we have not found it so far. Any help or direction regarding the hibernation issue as it relates to UPS power fail protection will be appreciated. Thanks again and best regards. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Power Fail Protection Update II
Many thanks once again to those that responded to my original posting (and my follow up message) with information about Network UPS Tools, other Linux-based tools like rtcwake, and commercial UPS products. We have quite a bit more evaluation and testing work to do before a power fail protection method is selected. I hope the discussion is as beneficial to others as it is to my organization. Along the way, one of our users pointed out that some of our CentOS 6 desktop/deskside machines actually throttle back power consumption in different ways than others. Instead of the yellow/amber LED display in the center of the power button, they flash green and then go solid green after the power button is pushed and the system wakes up. We have also noted that none of our CentOS 6 systems restart on their own when power is restored. This is the case whether power is lost during normal operation or when the systems are in a standby state when line power is lost. These two conditions or states (yellow/amber vs flashing green) have us wondering exactly what standby mode these systems are in and what settings may have been selected to send them to their standby state. Is there some sort of standard that applies to the standby states and are there BIOS settings or configuration files that control the what, how, and when standby is directed? Thanks to all and best regards. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Network Interrogation
Small private networks are a necessary part of our business. We also run some small networks with Internet connectivity through firewall routers. The smallest of these networks has only a printer and a mix of five CentOS and Windows 7 machines. We use a commercial protection product on the W7 system. This product has worked well guarding against unwanted software on the system for about three and a half years. Scans are scheduled and performed routinely once a week or on demand at various times. A recent update to this protection product has caused it to start probing the network for other systems. There is sometimes a message following scans indicating that there are other systems on our network that are unprotected. It appears that the two systems it is naming are a CentOS 6 system and the HP printer. This network probing does not happen with every scan that is run by the protection software and we have not been able to determine what causes that probing to be initiated. We also do not know exactly what is happening over the network during the probing activity. The protection software support folks have been no help in figuring out what is going on. There seems to be no good reason for the probing message to name only these two systems. The available printer status shows no indication of network traffic associated with this probing activity. The CentOS 6 system also does not indicate any related network activity from the system that is running the protection software. We have tried unsuccessfully to capture the network probing activity using Wireshark. Any ideas regarding how to track down what is happening here would be greatly appreciated. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 7 yum Issue
We have been following the email list discussion regarding recent problems with yum and the upgrade to the most current CentOS 7. We have also tried some of the remedies suggested or recommended. None of these measures has yielded success, and it is not totally clear whether or not our most recent yum issues have the same root cause as those experienced by others. Fortunately, our yum execution after the most recent updates came available was on one of our virtual machines. This is a CentOS 7 system running on VirtualBox and hosted on a Windows 7 system. It is typically used for verifying system updates and applications before they are introduced to regular Intel-based systems. This virtual CentOS 7 system has also been faithfully updated for over a year by using yum and accepting all updates when they become available. The truly remarkable thing is that yum does not finish with any identifiable errors. In fact it does not finish at all and seems to be in a continuous loop of some kind that has run up to ten minutes, so far. Information scrolling by seems to repeat every few seconds with the names of a set of packages repeating over and over. Many of the messages indicate package conflicts or a dependency problem of some kind. This "loop" never allows progress to the point where one would answer yes or no the to the updates. With no end in sight, we chose to kill the yum process. Shut down and restart of the current CentOS system yields a system that appears to work well with no issues related to killing the yum process. Four separate yum update sessions have been attempted, and all have been killed. All data has been backed up properly and our application reload plan is in place, with the exception of some from epel which have caused previous problems, that others have noticed recently also. Our current plan is to remove the current CentOS 7 virtual system and install the newest CentOS 7 available. We have no plans to run yum update on any other CentOS 7 systems. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Gulliver
We have been fortunate to hang onto one of our summer interns for part time work on weekends during the current school year. One of the intern's jobs is to load documents and data which are then processed. The documents are .txt, .docx, and .pdf files. The data files are raw sensor outputs usually captured using ADCs mostly with eight bit precision. All files are loaded or moved from one machine to another with sftp. The intern noticed right a way that the documents will transfer perfectly from our PPC and SPARC machines to our Intel/CentOS platforms. The raw data files, not so much. There is always an Endian (Thanks Gulliver) issue, which we assume is due to the bytes of data being formatted into 32 bit words somewhere in the Big Endian systems. It is not totally clear why the document files do not have this issue. If there is a known principle behind these observations, we would appreciate very much any information that can shared. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] USB Serial Ports
We have several CentOS 6 systems that are used in various configurations of test equipment. One of the primary functions of these systems is the connectivity to serial ports of some operational systems that have serial port control requirements. Lack of interface bus slots led us to the use of USB connected serial ports on these CentOS 6 systems. We first used these USB connected serial ports in our RHEL 5 test equipment systems. With RHEL 5, shut down and boot up of the systems would often cause the serial ports to have a different driver name, even though we had not changed the ports where the USB devices were plugged in. This caused software access problems until we discovered what could be done using the udev rules to lock in the driver names. This problem seems to have gone away in our newer systems with CentOS 6, and we would like to make sure that it does not return. We are deploying some of the systems and do not want to have software access issues in the field where fixes are more difficult. We would like to know if there is some underlying factor that has solved this problem for us. Any ideas on what to check would be greatly appreciated. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Intel Flaw
How does the latest Intel flaw relate to CentOS 6.x systems that run under VirtualBox hosted on Windows 7 computers? Given the virtual machine degree of separation from the hardware, can this issue actually be detected and exploited in the operating systems that run virtually? If there is a slow down associated with the fix, how much might it impact the virtual systems? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Audio Output Timer Utility
We have several CentOS 6.x systems that are incorporated into suites of special test equipment. One of the requirements for these systems is that they be kept up to date and they are kept up to date using yum once per week or more frequently, as needed. All of our CentOS 6.x systems have at least 2TB system disks and were installed with essentially everything that was available on the DVD at the time of initial setup. One of our programs is currently in Beta Test which includes both command line and GUI operator inputs and responses. The functional testing requires operator inputs or responses within certain time frames. This timing has usually been implemented with a stopwatch that is operated by a test director. Other timing options would beneficial for complex testing scenarios One of our test directors suggested that we use a digital count- down timer with audio outputs to prompt test operators for their inputs or responses at appropriate times. We have not found such a utility on our CentOS 6 distribution. If there is one available, we would appreciate any information that can be provided. Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Audio Output Timer Utility
Thanks for the information on festival.I think that this will work for at leastsome of our applications. On Tuesday, January 9, 2018 12:43 PM, Frank Cox wrote: On Tue, 9 Jan 2018 17:34:32 + (UTC) Chris Olson wrote: > One of our test directors suggested that we use a digital count- > down timer with audio outputs to prompt test operators for their > inputs or responses at appropriate times. We have not found such > a utility on our CentOS 6 distribution. Use the sleep command and festival. #!/bin/bash echo "one " | festival --tts sleep 5 echo "two" | festival --tts sleep 4 echo "ten thousand three hundred twelve " | festival --tts sleep 50 echo "operation complete" | festival --tts -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 autofs flakyness
We have had this problem before but not for a long time.The problem was eventually traced to a router (we think)and corrected when the old router was replaced. On Thursday, January 11, 2018 2:17 PM, "m.r...@5-cent.us" wrote: I have a user who couldn't get in via WinSCP to a server. Got him to log in via putty, and that was fine. But he still couldn't get in the other way. At my manager's suggestion, I restarted autofs... and everything worked. Note that his home director5y was already automounted via NFS, after he logged in via putty. We've seen other, similar oddities with NFS. Is anyone else seeing this, or have a clue? Btw, there were no errors showing in /var/log/messages, journal, I saw this in dmesg: task mount.nfs:83892 blocked for more than 120 seconds, but that was from four days ago, and my user just reported the problem yesterday, though he hadn't tried to use WinSCP in about a month. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] evince
We have some small networks with connectivity to the Internet through firewall routers. The smallest has one Windows 7 system and three Linux systems including both CentOS 6 and CentOS 7 machines. The Windows 7 systems have full Adobe packages that are updated regularly and are trouble free. On the Linux systems, evince has been our go to product for viewing and printing .pdf documents. This has worked well for at least four years. Some .pdf documents received recently from insurance companies and financial institutions appear to have a font problem that we have not been able to solve. Information available at the sites listed below have been no help. Previous font problems with various warnings have been solved automatically with substitution, but this does not seem to be working with these new files. The current problem leaves blank nearly half of the pages in some documents. Is there better source to look for answers than these two: http://www.gnome.org/projects/evince/ https://wiki.gnome.org/Apps/Evince Any help with this issue would be greatly appreciated. Thanks. [user@computer ~]$ uname -a Linux delle520 2.6.32-696.20.1.el6.x86_64 #1 SMP Fri Jan 26 17:51:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [user@computer]$ evince Plan.pdf Error: could not create type1 face some font thing failed Error: could not create type1 face some font thing failed o o o o ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Network Performance
One of our summer interns has stayed on working part time on weekends during the school year. This schedule presents an opportunity for technical investigations and some needed performance testing. The last weekend assignment included data rate testing on one specific network pathway. Checking out previous network testing was the first assignment. Some five year old, archived SPARC/Solaris and Intel/Solaris network tests included ftp runs like the following: ftp> ftp> put "|dd if=/dev/zero bs=32768 count=8000" /dev/null 200 PORT command successful. 150 Binary data connection for /dev/null (IP Address). 8000+0 records in 8000+0 records out 226 Transfer complete. local: |dd if=/dev/zero bs=32768 count=8000 remote: /dev/null 262144000 bytes sent in 23 seconds (11081.79 Kbytes/s) ftp> There were dozens of examples of such ftp tests with varying block sizes, bidirectional transfers, destination files on RAID storage, and a mix of some system loading programs run independently and during the network performance testing. Also archived were a full complement of network tests with what looks like the original ttcp and possibly newer versions. These utilities looked like they would work on our CentOS 6 systems, but we did not find ttcp and the ftp tests failed. the piping from dd failed with a message indicating that: |dd was not a recognized file. We no longer have available CentOS systems with versions of the OS before CentOS 6. Could there have been a change to ftp that will not allow a source file specified in this way or would this transfer method have never worked on Linux? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Network Performance Update
My thanks to all that responded to my posting about measuring network performance. Helpful suggestions are always very much appreciated. The type of testing that we were attempting does not appear to be a major topic of interest on the list but the additional information below may be helpful to some users. Initial reports of an issue with |dd not being recognized was questioned so several more tests were conducted. Testing the transfer to /dev/null was repeated several times with identical results as indicated immediately below. How this message about dd was interpreted as it not being recognized is not clear. What is clear is the Broken pipe indication which we then went on to investigate. All indications are that the destination of the pipe was not accepting the sourced data. With this in mind we conducted several successful transfers as indicated below. It appears that /dev/null is not a legitimate place to send data from an ftp transfer. This was the case even when the original source was a file and not a dd command. One of the suggestions in response to our original posting indicated that "|dd might be changed to |"dd. This was also tried as indicated below. Both forms of the put command that send the data to an actual file (zeros) work and were repeated several times. Using the form |"dd consistently runs slower than using the original put command format: "|dd Bottom Line: Mystery partially solved. What is left is why the /dev/null destination for the data does not work. Just about every other commands we tried routing data to /dev/null work from any user space. Attempting Transfer Of dd Created Output To /dev/null - ftp> ftp> put "|dd if=/dev/zero bs=32768 count=8000" /dev/null local: |dd if=/dev/zero bs=32768 count=8000 remote: /dev/null 227 Entering Passive Mode (192,168,1,101,27,154) 500 OOPS: ftruncate dd: writing `standard output': Broken pipe 1+0 records in 0+0 records out 0 bytes (0 B) copied, 9.3018e-05 s, 0.0 kB/s ftp> Successful Transfers Of dd Created Output To A File Named zeros --- ftp> ftp> put "|dd if=/dev/zero bs=32768 count=8000" zeros local: |dd if=/dev/zero bs=32768 count=8000 remote: zeros 227 Entering Passive Mode (192,168,1,103,164,178) 150 Ok to send data. 8000+0 records in 8000+0 records out 262144000 bytes (262 MB) copied, 26.4611 s, 9.9 MB/s 226 Transfer complete. 262144000 bytes sent in 27 seconds (9.7e+03 Kbytes/s) ftp> ftp> ftp> put |"dd if=/dev/zero bs=32768 count=8000" zeros local: |dd if=/dev/zero bs=32768 count=8000 remote: zeros 227 Entering Passive Mode (192,168,1,103,39,252) 150 Ok to send data. 8000+0 records in 8000+0 records out 262144000 bytes (262 MB) copied, 30.7971 s, 8.5 MB/s 226 Transfer complete. 262144000 bytes sent in 31 seconds (8.3e+03 Kbytes/s) ftp> ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Distributed System Monitoring
We have recently been assigned to help with the development of a system that will power non-computer/non-network devices located at various places within a 10,000 square ft facility. Most of these devices will operate on a fairly wide range of DC input power. The availability of surplus Cat-5 cable and the availability of low cost POE switches has been suggested as a method of powering these devices. There also appears to be some good, low cost installation options for all of the required system elements. The activity and health of the devices is directly related to their power consumption. Is there a standard CentOS feature or commonly used App that would facilitate monitoring the power being supplied by each of the individual POE switch outputs? Thanks in advance for any information shared. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS Virtual Machine System Time
We run several CentOS 6 and CentOS 7 systems as virtual machines using VirtualBox on Windows 7. Most of these systems have continuous up time. The Windows 7 foundation platforms have no difficulty keeping accurate system time unless they are shut down for some reason, which is rare in our environment. We generally restart the Windows 7 machines at leastweekly rather than performing a complete power up restart. The CentOS virtual machines are shut down at times, usually to switch between versions that support various applications and for updates using yum. When the virtual CentOS systems are brought up, the system time always matches the Windows 7 host system time. We have recently noticed that after several hours, the CentOS system time has started to lag behind. The time difference in a week can be as much as four days. This system time lag has not always been immediately discovered by the user resulting in some annoying file date issues. Access to some web sites have also been a problem due to the "date in the future" issue. We are now on the lookout for this system time problem and restart the virtual machine to set the current date and time. Is this a common time problem when running CentOS as a virtual machine? Any suggestions regarding the cause if this problem and how to keep the CentOS system time locked to the host platform time would be greatly appreciated. Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Shutdown/Poweroff
Is there a good source of information about how Linux distributions and installers identify and interact with the hardware devices in a system? We are particularly interested in the shutdown process that leads to complete power-off. Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Unusual System State
Our smallest network of systems has only four computers connected via Gigabit Ethernet. The oldest and most stable platform is an eight year old Dell E520 running CentOS 6.8. We often try out applications on this Dell/CentOS machine before moving them to other systems on our other networks. Last night, one of our users decided to create a single, 228GB home directory tar archive on an empty, 500GB, external, USB, Ext4 disk drive. This was obviously a poor decision. The extent of the results were not obvious until this morning. All disk activity had stopped and the system appeared to be hibernation. A push on the power button usually brings the system back to life, but in this case, the unlock screen was presented for only three seconds and then the hibernation mode was resumed. Repeated attempts to log on were all thwarted due to this behavior. ssh from other systems wasalso not possible. Holding the power button in order to initiate power down did not work either. The result was the same as a one second press of front panel power button bringing up the unlock screen for only a short time. We eventually removed the power cord for five minutes and then restarted the machine. The system is running normally once again. The corrupted file system on the USB disk has been restored by re-partitioning and building a new Ext4 file system on it. The user no longer gets to use external disks. Examination of log files and the dmesg output did not yield any useful information regarding the unusual state of the system when unlock logon was not possible. Is there somewhere else we should look for evidence of what actually happened and the unusual state of the system. Thanks. [user@computer ~]$ uname -a Linux computer 2.6.32-642.11.1.el6.x86_64 #1 SMP Fri Nov 18 19:25:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [user@computer ~]$ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ghostscript update breaks evince
Yes, it looks like evince is not working for .ps files on my system running fully up to date CentOS 6.8. Three years ago, a .pdf version of this file was created and it still displays as it should using evince. [user@computer Documents]$ evince DPS_2014_1443inv.ps & [1] 9865 [user@computer Documents]$ invalidaccess -7 invalidaccess -7 ** (evince:9865): WARNING **: Error rendering thumbnail invalidaccess -7 invalidaccess -7 [1]+ Done evince DPS_2014_1443inv.ps [user@computer Documents]$ On Wednesday, January 4, 2017 1:45 PM, "Phelps, Matthew" wrote: On Wed, Jan 4, 2017 at 3:21 PM, Robert Nichols wrote: > Today's ghostscript.x86_64 0:8.70-21.el6_8.1 update causes evince to > refuse to > display any postscript file. Running evince from a terminal session, I see > the > errors: > > invalidaccess -7 > invalidaccess -7 > invalidaccess -7 > > ** (evince:1252): WARNING **: Error rendering thumbnail > > Downgrading to ghostscript.x86_64 0:8.70-21.el6 corrects the problem. > > Anyone else seeing this? > > -- > Bob Nichols "NOSPAM" is really part of my email address. > Do NOT delete it. > > Yes. I'm seeing it too. CentOS 6.8 with all updates applied. -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Firefox Issue
Everyone is back at work and starting to use computers on our smallest network which has Internet access through a rather old Linksys router. Two systems were left on and screen-locked over the extra long weekend. There does not appear to have been any Internet access interruption in our absence. A Firefox browser on one system was left pointing to a commonly used web site: https://www.yahoo.com/. This Yahoo web page was not displayed when the user unlocked the screen and brought up the browser from the task bar. Instead, a site located at the link https://gaibacoupontec.com was displayed with a message indicating that there was an urgent Firefox update required. There was a button to download and to install the update. I killed the Firefox browser rather than getting rid of it with the X in the upper right hand corner. This event has the aroma of an unwanted cyber intrusion, which is why I killed the browser. I have also copied and stored the full URL displayed in the browser, but have only included the first part "https://gaibacoupontec.com"; here so as not to tempt anyone to risk access. Is it possible that a new Firefox flaw has been detected and is being exploited for malicious purposes? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Firefox Issue
We have several small networks, some of which have only four systems that are usually a mix of Windows 7 and CentOS 6 and CentOS 7 machines. All of these systems are Internet connected and updated regularly when yum finds packages available. Information about one of the CentOS 6 machines is included below. This system experienced a Firefox issue. [user@computer]$ uname -a Linux computer 2.6.32-754.3.5.el6.x86_64 #1 SMP Tue Aug 14 20:46:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [user@computer]$ Several weeks ago, one of the Firefox updates did something unusual. It changed the browser-stored home page to https://www.centos.org/ from the original home page file:///usr/share/doc/HTML/index.html. This original home page had been in place since 2014, and had survived all Firefox updates for a little over four years. Last week, someone left one browser running and the system went into power save mode. To wake the system up we used the standard method of a quick push of the power button on the front of the Dell tower system. Although the system seemed to be running, the monitor and mouse never came to life. We also could not ssh into the system from any other computer on the network. We decided to use a steady push on the power button to shut the system down. After powering up again, the system seemed to run normally, but the browser home page was back to file:///usr/share/doc/HTML/index.html. Has anyone else experienced such an issue with Firefox recently? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Address Codes
One of our summer interns has stayed on during the school year to work some weekends on special assignments. This past weekend, her assignment was to draft, and try out, procedures for scanning all incoming regular mail including the envelopes. This is a new effort for us because previous mail handling was done by another organization. Most of our incoming mail is from other businesses that create printed address labels. Many of these labels also have a type of bar code below the address. Is there a Linux utility or standard application that will read and translate these codes. Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Firefox Video Capability
One of our summer interns has stayed on during the school year to work some weekends on special projects. This past weekend, her assignment was to trouble shoot problems with Firefox when trying to view various on-line training videos. At some web sites, the video associated with the page will not play and we get the messages shown below. The Download statement is actually a link and was used to download this rpm file: adobe-release-x86_64-1.0-1.noarch.rpm. "Cannot Play Video" "The latest version of Adobe Flash is required to play this video." "Download the free Flash player here." The intern did not install this rpm because doing so outside of yum did not seem like a good idea. We also do not really know how the Adobe Flash utility is called up by Firefox and whether or not the installation would solve the problem or possibly cause other problems. This problem is not happening on our Windows 7 machines, but not everyone here has a Microsoft machine to use. On Windows, the Firefox occasionally updates itself when launched so that might explain the difference. The training videos always do play on Windows 7 systems when the web pages are brought up. We also noticed that on Windows 7 there are no Firefox related processes remaining after closing all Firefox browsers. This is not the case on our CentOS 6 systems as indicated in the output below. Is this video viewing issue a common problem, and if it is, can someone provide some direction to correct it. Thanks. ++ [user@computer ~]$ ps -elf | grep firefox 0 S user 3872 1 0 80 0 - 68607 poll_s Nov08 ? 00:00:00 /usr/lib64/firefox/bundled/libexec/at-spi-bus-launcher 0 S user 8178 8149 0 80 0 - 25832 pipe_w 19:42 pts/2 00:00:00 grep firefox [user@computer ~]$ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Disk Performance Issue
We have a very old Dell desk top machine that has been running CentOS 6 for the past five years. It received a new, 1 TB disk and additional memory before the OS installation. It has been the primary Linux machine in our smallest and most remote field office. It has been updated at least once a week and has all current dates installed. Boot-up this morning lasted about six times as long as usual. Disk access, as indicated by the disk activity light, is almost continuous and for extended periods of time when ever something is done that requires the disk. Everything observed happens whether or not the machine is connected to our network. All of our files appear to be accessible if one is patient. One theory put forward is that some application is running that uses up CPU and disk bandwidth. Another theory is that thereare disk errors, mostly corrected by EDCS features. We do not see any rogue applications and error logs show no disk issues. This is a mysterious issue that we hope to circumvent by putting a new disk and installing CentOS 7 from DVD. Our hope is that the current disk can be mounted externally on the new CentOS system using a USB to SATA adapter and that data can be moved off of the old disk. Advice regarding this issue and any possible diagnostic methods will be greatly appreciated. df -k output: +++ Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_delle520-lv_root 51475068 12110896 36742732 25% / tmpfs 1928152 176 1927976 1% /dev/shm /dev/sda1 487652 211073 250979 46% /boot /dev/mapper/vg_delle520-lv_home 905124888 246856176 612284356 29% /home +++ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] mplayer
We recently installed CentOS 7 from DVD. Our install selection was the GNOME desktop option. yum update yielded about 465 megabytes of updates all of which were successful with no warnings. The multi media option was not chosen because KDE was listed. GNOME was not apparent in the software list for the multi media workstation install. Google searches led us to instructions for installing mplayer. The repo update appears to be successful as indicated below. Dependency resolution at the time of mplayer installation yielded twelve errors. Are there other packages that could be installed prior to another attempt at mplayer installation that might provide the missing items? Might these errors have been avoided by choosing the multi media workstation install? Thanks. ++ [user@computer ~]$ yum repolist Loaded plugins: fastestmirror, langpacks Determining fastest mirrors * base: centos-distro.cavecreek.net * epel: mirrors.sonic.net * extras: centos-distro.cavecreek.net * nux-dextop: mirror.li.nux.ro * updates: centos-distro.cavecreek.net repo id repo name status base/7/x86_64 CentOS-7 - Base 10,019 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 13,237 extras/7/x86_64 CentOS-7 - Extras 419 nux-dextop/x86_64 Nux.Ro RPMs for general desktop use 1,603 updates/7/x86_64 CentOS-7 - Updates 2,137 repolist: 27,415 [user@computer ~]$ --> Finished Dependency Resolution Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libgnutls.so.26()(64bit) Error: Package: ffmpeg-libs-2.6.8-3.el6.nux.x86_64 (nux-dextop) Requires: libopenjpeg.so.2()(64bit) Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libcdio.so.10()(64bit) Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libcdio_cdda.so.0(CDIO_CDDA_0)(64bit) Error: Package: librtmp-2.4-0.3.20110811gitc58cfb3e.el6.nux.x86_64 (nux-dextop) Requires: libgnutls.so.26()(64bit) Error: Package: ffmpeg-libs-2.6.8-3.el6.nux.x86_64 (nux-dextop) Requires: libgnutls.so.26()(64bit) Error: Package: faac-1.28-2.el6.nux.x86_64 (nux-dextop) Requires: libmp4v2.so.0()(64bit) Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libcdio_paranoia.so.0()(64bit) Error: Package: ffmpeg-libs-2.6.8-3.el6.nux.x86_64 (nux-dextop) Requires: libgnutls.so.26(GNUTLS_1_4)(64bit) Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libcdio_paranoia.so.0(CDIO_PARANOIA_0)(64bit) Error: Package: librtmp-2.4-0.3.20110811gitc58cfb3e.el6.nux.x86_64 (nux-dextop) Requires: libgnutls.so.26(GNUTLS_1_4)(64bit) Error: Package: mplayer-1.1-33.20150505svn.el6.nux.x86_64 (nux-dextop) Requires: libcdio_cdda.so.0()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@root user]# ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] gedit font size
We recently installed CentOS 7 on a system. We chose the GNOME desktop install option and have used yum to install all of the available updates. The first run of yum update yielded about 450 megabytes of items to be installed or updated. All of the updates have been successful. One issue with our new CentOS system is that some users want to use gedit, but the displayed font size is extremely small. Internet searches for a way to increase font size have not yielded any useful information. Is there a standard method to make the gedit font size larger? Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Network Diagnostics
In our smallest office, we have a Dell CentOS 7 system, a Windows system and an HP 8610 printer, all hard-wire Ethernet connected with a Linksys router. The router provides Internet connection. All of the network-connected systems get their IP address from the router at power up. Successful network connection of the printer at power up has recently started taking much longer than usual. The display on the front of the printer indicates that it is initially attempting wireless connection even though this feature is turned off. Ethernet connection is eventually achieved and the printer functions normally on the network but just for a few minutes. After about five minutes, the printer drops its Ethernet connection and appears to be attempting wireless connection once again. During this period, network connectivity is disrupted for the other systems on the network. They are not able to communicate with each other or access the Internet through the router. Turning off the printer restores network connection for the other systems. One of our personnel at another office suggested using Wireshark to check out the network when the printer is having difficulty. Wireshark was apparently not on this system so we installed it using yum install. The tail end of the apparently successful installation process is shown below. Unfortunately, we cannot seem to find Wireshark on the system. Is it possible that Wireshark was not actually installed or do we just not know how to locate and use it? Is this printer networking issue a known problem and is Wireshark the right tool to diagnose the problem? Thanks. Installed: wireshark.x86_64 0:1.10.14-16.el7 Dependency Installed: libsmi.x86_64 0:0.4.8-13.el7 Complete! [user@computer ~]$ [user@computer ~]$ which wireshark /usr/bin/which: no wireshark in (/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/user/.local/bin:/home/user/bin) [user@computer ~]$ Recent successful installations: [user@computer ~]$ [user@computer ~]$ which mplayer /usr/bin/mplayer [user@computer ~]$ which ffmpeg /usr/bin/ffmpeg [user@computer ~]$ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] System Time
A few years ago, one of our interns was curious about system time keeping features in computer systems. This intern was also the proud owner of an inexpensive Radio-Controlled Clock. The intern wondered why computer motherboards were not just equipped with a chip like the ones in the RCC so that their system time would always be correct. I posted a question about this on the CentOS email list and received more responses than those postings about problems with the new Firefox release. I must have really struck a very sensitive system time nerve. This large response was a bit of a surprise and included a bunch of time related horror stories. It became clear why using an RCC chip on motherboards would NOT be a good idea. GPS network time servers seemed to be a preferred choice. All of our bedrooms have Radio-Controlled Clocks. At 5:30 this morning, half of the clocks displayed the correct time. The other half of the clocks were incorrectly showing a time one hour ahead. Maybe this is one more piece of evidence to reject using an RCC time base for computers, at lease in thestate of Arizona. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] rpm command option
We located an application recommended by one of customers for sharing certain data. It was available for installation using a few different methods. Using yum was also recommended for the installation. The install instructions began with what appeared to be a fairly typical command as indicated below (with the URL slightly altered). sudo rpm --import https://rpm.x.com/rpmrepo.key To our junior employee assigned to perform the install on a test system, it seemed like a good idea to do some checking on the rpm option --import indicated in those instructions. They did not find the --import in any of the 14 pages of the CentOS 7 man page for rpm. Some Google searches indicated that the --import option does exist. The repo setup and application installation all went well and took only about three minutes. The app is also working as intended. Is there some good reason for --import being left out of the manual page? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
