On Sun, 7 Jul 2002, Dan Kenigsberg wrote: > On Sun, Jul 07, 2002 at 03:16:28PM +0300, Tzafrir Cohen wrote: > > On 7 Jul 2002, Gilad Ben-Yossef wrote: > > > > > On Sun, 2002-07-07 at 15:43, Michael Sternberg wrote: > > > > > > > > Is it advisable in case of such failure to start computer with a random > > > > static IP and continue to look for DHCP server in background ? > > > > This way the boot process will be at least continued.. > > > > > > Choosing addresses at random is verbotten and will get your BOfH to come > > > chase you around the office with a big LART. You already have a local > > > loopback address (127.0.0.1) it should be enough provided you have a > > > /etc/hosts file that maps that to your machine name. > > > > So you think that when dhcpcd fails the system (the script running it) > > should rewrite /etc/hosts to map the host name to 127.0.0.1 ? Is this done > > anywhere? > > > > What is 169.254.0.0/16 ? > > I believe that keeping the interface down is the best option - I only wish it > kept trying...
cron to the rescue? a cron job that runs every 5 minutes: if eth0 is up exit 0 if exists file /var/lock/dhcpd/shlodnt_try_to_run exit 0 a_test_for_an_alrteady_runing_dhcp exit 0 ifup eth0 -- Tzafrir Cohen /"\ mailto:[EMAIL PROTECTED] \ / ASCII Ribbon Campaign Taub 229, 972-4-829-3942, X Against HTML Mail http://www.technion.ac.il/~tzafrir / \ ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]