02-Apr-02 at 17:16, Adam Shostack ([EMAIL PROTECTED]) wrote : > The client's clock is running a few minutes behind the server. You > write the file at local noon, which the server sets to be 12:03. Mutt > checks the file, sees that its mtime is in the future (12:03 being > later than 12:00), and warns you.
NTP is your friend. I use NTP to synchronise all servers, and as many workstations as possible. Everybody's clock is within microseconds of each other, and this can reduce problems. Using a simple ntp client like k9, you can just listen for ntp broadcasts on the local subnet and update your clock accordingly. k9 works for Windows and Linux clients. You just need one "master" server on each subnet, which broadcasts the time every minute or so to all clients. -- [Simon White. vim/mutt. [EMAIL PROTECTED] GIMPS:61.19% see www.mersenne.org] If it dies, it's biology. If it blows up, it's chemistry, and if it doesn't work, it's physics. [Linux user #170823 http://counter.li.org. Home cooked signature rotator.]
