[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem with DHCLIENT vs 64-bit time_t
- Subject: Problem with DHCLIENT vs 64-bit time_t
- From: drosih at rpi.edu (Garance A Drosihn)
- Date: Mon Feb 16 19:24:46 2004
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_(_at_)_gilead_(_dot_)_netel_(_dot_)_rpi_(_dot_)_edu
Senior Systems Programmer or gad_(_at_)_freebsd_(_dot_)_org
Rensselaer Polytechnic Institute or drosih_(_at_)_rpi_(_dot_)_edu
Visit your host, monkey.org