Best of Technical Support
My PPP connection is failing while using a modem to dial up to my ISP. My log indicates (after chat):
pppd:Serial Connection established pppd:Using interface ppp0 pppd: Connect: ppp0 /dev/ttyS2 pppd: LCP: timeout sending Config-Requests pppd: Modem Hangup pppd: Connection terminated pppd: Exit
My options file with and without these lines given separately had the same effect:
lock passive lcp-echo-failure 10 lcp-echo-interval 400Chat (tried different values):
'' 'AT&F' (also used ATZ) 'OK' 'ATDTxxxxxx' 'CONNECT' '' 'login:' 'xxxxxx' 'password:' 'xxxxxx' 'TIMEOUT' '60'pppd options (also tried 1500 for MTU and MRU:
hardflowcontrol=yes defroute=yes MRU=556Do I need to include something more in my chat to make the modem wait longer ? Also, according to my ISP administrator, my machine is “not replying to LCP request”. My modem is a BestData 56K internal modem (#56SF), controller-based. I am using Red Hat 6.0 Intel. —Vijay Nunna, email@example.com
There isn't anything else you should include in your chat script; however, some servers may be slow to start up the LCP communication, and thus your pppd daemon will timeout before then. To raise the number of LCP configure-request packets before pppd determines it is not responding, you can add the lcp-max-configure option to your /etc/ppp/options file, followed by the number of LCPs to send. For example, lcp-max-configure 30 would raise the number from the default of 10 to 30. You might also want to remove the—Andy Bradford, firstname.lastname@example.org
You need to add debug on your pppd command line and look at the /var/log/messages file. You also want to replace chat with chat -v. Those two combined will give you lots of debug output and hopefully a better idea of what is failing and where. —Marc Merlin, email@example.com
I am trying to install a package that includes a Ghostscript driver for my printer. I'm getting dependency issues. The files required (as printed by rpm) are:
libc.so.6(GLIBC2.0) libc.so.6(GLIBC2.1) libm.so.6(GLIBC2.0) libm.so.6(GLIBC2.1)
I've upgraded the libc libraries to glibc 2.1, but this seemed to have no effect. Looking at the dependency list, it also seems to need libc.so.6 and libm.so.6 without the GLIBC attached, and it has no problem finding these. I've looked at FTP sites for files with these names and cannot find them. Can anyone tell me what these are and if I need to find them, or whether I can tell rpm to ignore them? —Doug Morgan, firstname.lastname@example.org
Often, a dependency on libc6 or libm6 means only that the binaries were compiled to use these versions of the libraries—they can often be recompiled against an older libc/libm without any problems. To do this, grab the SRPM (it should have the extension .src.rpm), do
and install the resulting binary .rpm. Use this approach with caution, as there are applications that exhibit bugs under the older libc/libm (or won't compile). Still, in my experience, it generally works just fine. —Scott Maxwell, maxwell@ScottMaxwell.org
Although you can install glibc 2.1 on a glibc 2.0 system, it may be better for you to upgrade your system to SuSE 6.3 instead. However, if you do have all the libraries installed, but for some reason the RPM database doesn't agree, you can force the package to install with rpm --nodeps package.i386.rpm.
Another option is to get the .src.rpm version of your package and rebuild it for your system: rpm --rebuild package.src.rpm. The resulting package should be in /usr/src/redhat/RPMS/i386/. —Marc Merlin, email@example.com
I am thinking of building a dual-processor computer and wondering if Linux supports this. I have heard Linux is the best OS, and I have heard Windows NT is the only OS that supports multi-processing. —William Cason, firstname.lastname@example.org
Linux does indeed support SMP. In fact, I use a fast dual-CPU Linux box at work. —Scott Maxwell, maxwell@ScottMaxwell.org
Linux may or may not be “the best”, depending on what you're trying to do and what you're looking for. It does support multi-CPUs on recent kernels (2.2.x), and some distributions like Red Hat support SMP at install time. Some require you to compile your own kernel. —Marc Merlin, email@example.com
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide