Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
12-11-2001, 02:55 AM
|
#1
|
LQ Newbie
Registered: Dec 2001
Location: Sydney, NSW, Australia
Distribution: Redhat 7.1
Posts: 5
Rep:
|
Activating eth0 causes problems/delays in login... Why? And how to remediate?
Well, everything is already said in the subject field. I successfully installed an ethernet card, hooked my workstation to a LAN's firewall. But as soon as eth0 is activated, the login procedure is either dramatically delayed (when performed from the current X session) or simply fails (when performed from consoles). Conversely, the behaviour of the login procedure goes back to normal as soon as eth0 is deactivated.
Does anyone have any idea why? and how to remediate?
Many thanks in advance.
Eric
|
|
|
12-11-2001, 04:52 AM
|
#2
|
Member
Registered: Jun 2001
Location: Fairfax, California
Distribution: RH 9.0, RH 7.3, Mandrake 8.0
Posts: 986
Rep:
|
You'll need to be a little more specific.
1. Give us more info concerning your system (CPU type, model of NIC, distro and version of Linux, how do you connect to the outside world, etc.).
2. Are you using a static IP, or are you getting your IP via DHCP? (it sounds like a DHCP issue).
3) If DHCP, are you using pump, or dhcpcd?
4) Reserved for later questions; depends on the answers to 1-3.

|
|
|
12-11-2001, 05:14 AM
|
#3
|
LQ Newbie
Registered: Dec 2001
Distribution: RH 7.1, 9.0
Posts: 5
Rep:
|
hmm
I had the same issue when I changed the hostname under network config. It took up to 5 mins to boot completely!
All seemed well when I finally changed the name back (took me a while to think of that plan). Hopefully, this can be of help to you.
|
|
|
12-11-2001, 07:03 PM
|
#4
|
LQ Newbie
Registered: Dec 2001
Location: Sydney, NSW, Australia
Distribution: Redhat 7.1
Posts: 5
Original Poster
Rep:
|
[DMR] Let me be a little more specific
First of all, thx a lot to both of you for replying so promptly
[DMR] Here is more detail about my system
CPU: PIII i686 1GHz
NIC: Netgear something (it works perfectly fine, i can http, ssh, etc.)
Distro/Linux: Redhat 7.1 / 2.4.9-12
Static IP: 192.168.0.181
[wushu3d] I also have recently change the name of my host from the initial 'localhost.localdomain' to something more original, which i would not mind keeping :-)
Could my problem be related to pam.d or ipchains? My intuition is that the fact that the network/eth0 is enabled results in a change in the way password check is operated. There must be a configuration file somewhere, which i am not aware of, to indicate that password check remains local to the host...
--
Eric
|
|
|
12-14-2001, 07:18 AM
|
#5
|
Member
Registered: Oct 2001
Location: Lilburn, Ga.
Distribution: RH
Posts: 77
Rep:
|
This is often a sendmail problem. Try this: Disable sendmail startup and see if the boot proceeds normally. If so, sendmail is attepting to verify the DNS addy of the box's name by going to the default DNS servers. If the name won't look up, there is a long hang before sendmail gives up and allows the boot to proceed. This is only apparent when there is a network connection, as sendmail "knows" about that, and skips the lookup when not networked. Often seen after assigning some random name to the box.
|
|
|
All times are GMT -5. The time now is 06:58 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|