Date: Sun, 15 Feb 2004 18:22:36 -0600 (CST) From: matt <matt@grogged.dyndns.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: sparc64@freebsd.org Subject: Re: 64 bit time_t oddness Message-ID: <20040215181937.A30161@grogged.dyndns.org> In-Reply-To: <p06020413bc55b74e1ace@[128.113.24.47]> References: <p06020407bc533f0ae9d2@[128.113.24.47]> <20040215060047.GA62840@dhcp01.pn.xcllnt.net> <20040215165913.M30161@grogged.dyndns.org> <p06020413bc55b74e1ace@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Killing dhclient brought things back to normal - and yes, I did remove /var/db/dhcp.leases (had to, dhclient wouldn't work until I did). My kernel was just a run of the mill GENERIC, no changes. -m > > I am not seeing this behavior. My 64-bit time_t system is sitting > at 99% to 100% idle. One thing I notice is that you're running > dhclient there, and I am not. (I did do some testing with a DHCP > setup, but not much). Is your ethernet connection configured > correctly? Did you remember to remove /var/db/dhclient.leases ? > > I wonder if there's anything else that needs to be done for people > who are using DHCP. > > Do you have any interesting options turned on (or off) in your > kernel? My kernel == the GENERIC kernel, except that I have > commented out the WITNESS and WITNESS_SKIPSPIN options. I am > running the ULE scheduler (SCHED_ULE), which was a recent > change to the GENERIC kernel. Are you using the older scheduler? > > -- > Garance Alistair Drosehn = gad@gilead.netel.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040215181937.A30161>