Networking initialisation
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Unix and Linux reviews > Free Debian support > Linux Debian support > Networking initialisation




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Networking initialisation  
mapkyca


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-30-07 12:13 AM

Folks,

I have two machines, a client and a server. Both are debian. The
client mounts /home via NFS and loads users via NIS from the server.

Ever since upgrading my client to Debian 4 it takes several trys to
boot the client. 4/5 times the boot will halt at the YP bind stage and
will eventually time out, forcing me to restart.

After looking around, it seems that this problem is caused by the new
way that the networking subsystem is initialised, however nobody has
come up with a fix that works...

I have tried the suggested fix - add allow hotplug to interfaces, but
this has no effect.

How hard would it be, and what would I have to do in order to use the
old method of network initialisation which never had any problems?

Cheers,

M






[ Post a follow-up to this message ]



    Re: Networking initialisation  
AJackson


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-30-07 06:13 PM

On Jul 29, 10:25 pm, mapkyca <mar...@dushka.co.uk> wrote:
> Folks,
>
> I have two machines, a client and a server. Both are debian. The
> client mounts /home via NFS and loads users via NIS from the server.
>
> Ever since upgrading my client to Debian 4 it takes several trys to
> boot the client. 4/5 times the boot will halt at the YP bind stage and
> will eventually time out, forcing me to restart.

I would guess that you have some problems with resolving names on
machines.
You might want to set your server host name in /etc/hosts directly.
And have that
when you mount your NFS volumes.

(You might want to check nscd if you use NIS to look up names, as it
caches them.  But not until your NIS works)

> After looking around, it seems that this problem is caused by the new
> way that the networking subsystem is initialised, however nobody has
> come up with a fix that works...
>
> I have tried the suggested fix - add allow hotplug to interfaces, but
> this has no effect.

You could try autofs.  It works for me.  It only mounts file systems
when needed.
And the NFS home file system isn't needed until you log in.

> How hard would it be, and what would I have to do in order to use the
> old method of network initialisation which never had any problems?

No clue on that one.

> Cheers,
>
> M

--
Ingemar Bergman is dead.  Died in his home at F=E5r=F6






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 05:20 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register