php-windows Digest 30 Jun 2005 01:22:26 -0000 Issue 2712
Topics (messages 26160 through 26162):
Timezone Issue
26160 by: Andrew Ferguson
[suspicious - maybe spam] Amazing Funding simplified
26161 by: Aundrea Shipley
Problems with shell_exec() running .bat with For /F
26162 by: Fred
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
I first noticed this problem a few weeks back. When I log into
squirrelmail, the time displayed it eight hours ahead of the actual
time. I restarted my apache server and the problem was fixed. A few hours
later, the time is off again. This repeats, add infinitum.
Here's what's weird. Window's always reports the correct time, Window's
always reports the correct time zone too (-0700 US/Pacific). I run
date("O") and right after I restart apache, it will report -0700.
However, when I check back later it will report +0100. I ran
getenv('TZ') and that always reports US/Pacific. Any thoughts?
I'm running Windows Server 2003, Apache 2.0.53, and PHP 4.3.11.
-Andrew Ferguson
--- End Message ---
--- Begin Message ---
How are you?
Homeowner
You have been pre-approved for a $435,716 Home Loan at a 3.19 Fixed Rate.
This offer is being extended to you unconditionally and your credit is in no
way a factor.
To take Advantage of this Limited Time opportunity
All we ask is that you visit our Website and complete
The 1 minute post Approval Form
http://xLc.easyrate-loans.com/4/index/ryn/laz5N
Look Foward to Hearing From You,
Aundrea Shipley
--- End Message ---
--- Begin Message ---
PHP5 - Apache2 - XPSP2
I have an XP batch file incorporating a For /F command which behaves
strangely if run from a shell_exec() or system().
Specifically, if the batch is run from a command prompt or from the
scheduler, it works as expected, but if I run the same batch from
shell_exec() the For /F misbehaves interpreting token fields.
Paraphrasing, "For /F "tokens=1-4" %%a in ('dir /-c c:\somedir') do if /I
%%d==somevalue dosomething" always returns the fourth space delimited field
for %d when run fom an XP cammand prompt or scheduler, but sometimes returns
the third space delimited field when run from shell_exec(). It always
returns the wrong field from the same dir output lines. The only coincidence
seems to be that it returns the wrong field when there are lots of
consecutive spaces preceeding the field.
Got me beat.
Anyone had similar issues? Please?
--- End Message ---
