I know we’ve discussed this before, but I’m still having a problem with
empty tickets. Simply moving the transaction to the correct directory fixes
the problem, but every night I have 5-10 tickets to move in this manner and
it’s getting old.
Does anyone have any idea how to correct this time shift that is occuring?
For those that are unfamiliar with this, it seems that the date put into
the SQL database is on a different time zone than the rest of the machine.
and anything that is recieved between 9pm and 12 pm my time gets put into
the directory for today, but recorded as being in the directory for
tomorrow.
Any suggetions at all? I’ve looked at everything I can think of related to
time on that server.
If you have a problem with SELECT NOW()' returning values in GMT and not your local time, you have to set the TZ’ environment variable to
your current timezone. This should be done for the environment in which
the server runs, for example in safe_mysqld' or mysql.server’. *Note
Environment variables::.On Wed, 23 May 2001, Split infinity Tech Support wrote:
I know we’ve discussed this before, but I’m still having a problem with
empty tickets. Simply moving the transaction to the correct directory fixes
the problem, but every night I have 5-10 tickets to move in this manner and
it’s getting old.
Does anyone have any idea how to correct this time shift that is occuring?
For those that are unfamiliar with this, it seems that the date put into
the SQL database is on a different time zone than the rest of the machine.
and anything that is recieved between 9pm and 12 pm my time gets put into
the directory for today, but recorded as being in the directory for
tomorrow.
Any suggetions at all? I’ve looked at everything I can think of related to
time on that server.
–timezone=#
Set the timezone (the TZ) variable to the value of this parameter.
with safe_mysql scriptOn Wed, 23 May 2001, Split infinity Tech Support wrote:
I know we’ve discussed this before, but I’m still having a problem with
empty tickets. Simply moving the transaction to the correct directory fixes
the problem, but every night I have 5-10 tickets to move in this manner and
it’s getting old.
Does anyone have any idea how to correct this time shift that is occuring?
For those that are unfamiliar with this, it seems that the date put into
the SQL database is on a different time zone than the rest of the machine.
and anything that is recieved between 9pm and 12 pm my time gets put into
the directory for today, but recorded as being in the directory for
tomorrow.
Any suggetions at all? I’ve looked at everything I can think of related to
time on that server.
is the command in the init script that starts MySQL
Still loging as Eastern time, 3 hours ahead
Also, is there any way to fix this listserv so that replies are sent to the
list and not to both the user and the list, I have no need for two copies
of each reply.
Jason
Split Infinity
As a followup try using;
–timezone=#
Set the timezone (the TZ) variable to the value of this parameter.
with safe_mysql script
I know we’ve discussed this before, but I’m still having a problem with
empty tickets. Simply moving the transaction to the correct directory
fixes
the problem, but every night I have 5-10 tickets to move in this manner
and
it’s getting old.
Does anyone have any idea how to correct this time shift that is
occuring?
For those that are unfamiliar with this, it seems that the date put
into
the SQL database is on a different time zone than the rest of the
machine.
and anything that is recieved between 9pm and 12 pm my time gets put
into
the directory for today, but recorded as being in the directory for
tomorrow.
Any suggetions at all? I’ve looked at everything I can think of related
to
time on that server.
is the command in the init script that starts MySQL
Still loging as Eastern time, 3 hours ahead
Also, is there any way to fix this listserv so that replies are sent to the
list and not to both the user and the list, I have no need for two copies
of each reply.
You checked your systems TZ or timezone setting? I assume you are
on linux?
Also, shouldn’t the timezone value be PST8PDT ?
This is linux, RH7.0 to be exact. there is no default TZ setting for normal
logins, system time is set using PDT. I tried changing to PST8PDT with no
effect.
is the command in the init script that starts MySQL
Still loging as Eastern time, 3 hours ahead
Also, is there any way to fix this listserv so that replies are sent to
the
list and not to both the user and the list, I have no need for two
copies
of each reply.
is the command in the init script that starts MySQL
Still loging as Eastern time, 3 hours ahead
Also, is there any way to fix this listserv so that replies are sent to the
list and not to both the user and the list, I have no need for two copies
of each reply.
Jason
Split Infinity
As a followup try using;
–timezone=#
Set the timezone (the TZ) variable to the value of this parameter.
with safe_mysql script
On Wed, 23 May 2001, Split infinity Tech Support wrote:
I know we’ve discussed this before, but I’m still having a problem with
empty tickets. Simply moving the transaction to the correct directory
fixes
the problem, but every night I have 5-10 tickets to move in this manner
and
it’s getting old.
Does anyone have any idea how to correct this time shift that is
occuring?
For those that are unfamiliar with this, it seems that the date put
into
the SQL database is on a different time zone than the rest of the
machine.
and anything that is recieved between 9pm and 12 pm my time gets put
into
the directory for today, but recorded as being in the directory for
tomorrow.
Any suggetions at all? I’ve looked at everything I can think of related
to
time on that server.
And I’m told we do share some common rituals. Our “flame war” is apparently
held in person in their land and called “project meeting”.
-Alan Cox [on “Suits”]
I suspect that your sendmail is running with a different concept of the
current
timezone than your apache.
Has the box ever changed timezones?
Nope, it was installed for the sole purpose of running RT. Never had to
change timezones.
what’s the content of /etc/timezone?
That file does not exist.
Oh, and none of the lists hosted on fsck.com will be configured for
Reply-To-List.
Why is that? It seems the most logical way to do it. I mean, it would be
one thing if the list even had the “Mailing-list” headers so properly
equiped mail readers could just reply to list, but they aren’t there so one
must either reply to all (seems to be everyone’s prefered method) or reply
and change the To: field. That’s just silly to me.
Modern MUAs are capable of doing the right thing for list replies, however
this is a debate that WILL NOT happen on this list. If anyone would
care to debate this point, send me personal mail and I’d be happy to set up reply-to-list-discussion@lists.fsck.com.
Any e-mail sent to the SLA will immediately become the intellectual property
of the SLA and the author of said message will enter into a period of
indentured servitude which will last for a period of time no less than seven
years.
Modern MUAs are capable of doing the right thing for list replies, however
this is a debate that WILL NOT happen on this list. If anyone would
care to debate this point, send me personal mail and I’d be happy to set up reply-to-list-discussion@lists.fsck.com.
Any e-mail sent to the SLA will immediately become the intellectual property
of the SLA and the author of said message will enter into a period of
indentured servitude which will last for a period of time no less than seven
years.
Modern MUAs are capable of doing the right thing for list replies,
however
this is a debate that WILL NOT happen on this list. If anyone would
care to debate this point, send me personal mail and I’d be happy to
set up reply-to-list-discussion@lists.fsck.com.
Any e-mail sent to the SLA will immediately become the intellectual
property
of the SLA and the author of said message will enter into a period of
indentured servitude which will last for a period of time no less than
seven
years.
When mail comes into that box, what timezone does the Recieved line have in
the headers?On Wed, May 23, 2001 at 03:48:00PM -0700, Split infinity Tech Support wrote:
I’d suggest poking around the mysql documentation, I know that postgres
allows you to set timezone’s and format’s, I only assume mysql does too.
Any e-mail sent to the SLA will immediately become the intellectual property
of the SLA and the author of said message will enter into a period of
indentured servitude which will last for a period of time no less than seven
years.
I’ve seen this happen when using qmail and Mailman together.
qmail isn’t honoring TZ somewhere and mailing list email ended up
with a -0000 timezone. The admin I was working with gave up and we
switched back to sendmail which was what we were trying to convert
from. (I have since seen the light and joined the PostFix crowd for
all new installations unless we’re using smarthost/nullclient .cfs.)