Date: Mon, 16 Feb 2004 22:08:03 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: matt <matt@grogged.dyndns.org> Cc: sparc64@freebsd.org Subject: Re: Problem with DHCLIENT vs 64-bit time_t Message-ID: <p06020428bc57317ebef7@[128.113.24.47]> In-Reply-To: <20040216202835.D31791@grogged.dyndns.org> References: <p06020407bc533f0ae9d2@[128.113.24.47]> <20040215060047.GA62840@dhcp01.pn.xcllnt.net> <p0602040ebc54c885236b@[128.113.24.47]> <20040215165913.M30161@grogged.dyndns.org> <p06020425bc571c20bcde@[128.113.24.47]> <20040216202835.D31791@grogged.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:36 PM -0600 2/16/04, matt wrote: >I hate to add to the problems instead of proposing solutions, >but I noticed that /etc/periodic/weekly/310.locate seems to >be broken after the 64 bit time_t switch. Hey, the problems are there whether you report them or not! It's better that we find out about them, and maybe solve some of them before making everyone switch. What problems did you see with it? I just ran the script by hand on my 64-bTT system, and it seemed to work fine for me. Do you get error messages in /var/log/messages? What happens if you run it by hand? Eg: /usr/src/usr.bin/locate/code Or is this an issue with 'cron', where it is forgetting to run some of it's events? -- 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?p06020428bc57317ebef7>