| 1 |
On 07/05/2013 18:47, Tanstaafl wrote: |
| 2 |
> On 2013-05-07 11:43 AM, J. Roeleveld <joost@××××××××.org> wrote: |
| 3 |
>> Tanstaafl<tanstaafl@×××××××××××.org> wrote: |
| 4 |
>>> Ok, I've googled and can't figure this out... |
| 5 |
>>> |
| 6 |
>>> /etc/timezone is set to the correct timezone (EST5EDT) |
| 7 |
>>> |
| 8 |
>>> Date command says the server time is correct. |
| 9 |
>>> |
| 10 |
>>> Cron jobs run at the correct times. |
| 11 |
>>> |
| 12 |
>>> EMails generated by cron have a time one hour in the past. |
| 13 |
>>> |
| 14 |
>>> Looking at the email header shows the correct date/time stamps, but |
| 15 |
>>> since Thunderbird by default uses the date/time header set by the |
| 16 |
>>> client, it shows up as arriving an hour earlier than it actually did. |
| 17 |
>>> |
| 18 |
>>> Anyone? |
| 19 |
> |
| 20 |
>> Check the time in the headers of the email from the cronjob. It might |
| 21 |
>> be that this is caused by a different time (zone) of the mailserver |
| 22 |
>> or machine you are checking mail with. |
| 23 |
> |
| 24 |
> Nope. It is our mail server, here in our office... |
| 25 |
> |
| 26 |
> Also, I have rkhunter running on the same machine (job is in |
| 27 |
> /etc/cron.daily, instead of the root crontab), which generates its own |
| 28 |
> emails, and those have the correct time on them (header time matches |
| 29 |
> what is in the log). |
| 30 |
> |
| 31 |
|
| 32 |
|
| 33 |
Are you saying that scripts which do mail correctly (i.e. by themselves) |
| 34 |
work fine? |
| 35 |
|
| 36 |
But when you rely on crond to send the mail by grabbing STDOUT, then the |
| 37 |
time is wrong, and that this is consistent? |
| 38 |
|
| 39 |
That would point to something with crond and would need a few tests such |
| 40 |
as what happens with other crons from other users, what happens when you |
| 41 |
downgrade cron and then test? |
| 42 |
|
| 43 |
I'm assuming you use vixie-cron. Correct? |
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
-- |
| 48 |
Alan McKinnon |
| 49 |
alan.mckinnon@×××××.com |
Archives