On Wed, 14 Nov 2001, David Talkington wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> >> >Is there a way to give infinite leases to DHCP clients? > >> > > >> >Well, you can give the operational equivalent of it by giving it extremely > >> >large lease times in dhcpd.conf. For example: > >> > >> What problem does this solve? > > > >I didn't say I was trying to solve his problem. His post really had two > >parts: help solve my problem; and how do you give infinite leases. > > > >I answered the infinite leases question. Not that it solves his problem, > >because it won't. > > Right. Years of public service have taught me that the first > reaction, when someone comes to me and says, "How do I make this > convoluted solution work?", should always be skepticism. People have > a nasty habit of half-solving their problems and bringing me the mess > they made, instead of coming to me at the ground level to help them > define the real problem. So our job is to gently help them see the > forest through the trees. =) >
I agree. I don't usually just give people what they ask for because it's often not what they need. However, in this case, the dhcp leases info is actually useful for some people (it's what I use in my community center installations). So, I included a whole dhcpd.conf file. Maybe I'll attempt to help him solve the problem. He doesn't know that dhcpd is actually functioning. Also, the funky Windows dhcp client can be exasperating, too. For example, I just found a place where 2 PC's (new ones just added) couldn't get dhcp-assigned numbers, but 5 others appeared to be working. The local system manager did not check his chains box to see if dhcpd was actually running. He thought maybe we had bad cards in the new box, but what was really happening is that the machines that had been working were only making it look like they were getting a number from dhcpd; in reality they were just remembering what they had used before (funky client). When I got him to actually look at the server, found out that dhcpd was not running successfully because the system disk had filled up (probably from some repeated error message). Cleaning up some space, restarting, restarting the PC's cleared up the problem. In this case, the wonderful clients on the Doze boxes confused this guy and masked the real problem. Like I said, maybe I'll take a moment and read about the symptoms. > - -d > > - -- > David Talkington > http://www.spotnet.org > > PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp > > -----BEGIN PGP SIGNATURE----- > Version: PGP 6.5.8 > Comment: Made with pgp4pine 1.75-6 > > iQA/AwUBO/LgOL9BpdPKTBGtEQJZrACgl/5iG4k88qpH+Uf0aFZePqQfSCAAoJt5 > mAnD1oaopnrt0rAmTnoYa5YS > =zBjb > -----END PGP SIGNATURE----- > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > -- *************************************************************************** Jerry Winegarden OIT/Technical Support Duke University [EMAIL PROTECTED] http://www-jerry.oit.duke.edu *************************************************************************** _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list