Or they use Google Alerts.
On Thu, Oct 21, 2010 at 11:45 AM, Hamish Campbell <[email protected]> wrote: > Or they're lurking around here somewhere. > Kind Regards, Jochen Daum P.S.: Do you know anyone who wants to rent a desk in our Mt Eden office? http://ow.ly/2Vs5i - no term commitment - fully serviced Chief Automation Officer Automatem Ltd Phone: 09 630 3425 Mobile: 021 567 853 Email: [email protected] Skype: jochendaum Website: www.automatem.co.nz http://twitter.com/automatem http://nz.linkedin.com/in/automatem http://www.xing.com/go/invite/3425509.181107 http://www.aucklandbusinessnetworking.co.nz > On Oct 21, 10:13 am, Super Steve <[email protected]> wrote: >> Thanks guys! >> >> I've just run the same test again this morning and iServe are now >> reporting the correct time, so looks like it was an error at their end >> that they fixed without me having to report it. >> >> On Oct 20, 6:10 pm, Simon J Welsh <[email protected]> wrote: >> >> >> >> >> >> >> >> > They're both in the same timezone and are giving a difference of about >> > 3613 seconds in their timestamps (which timezones/DST shouldn't change), >> > so it looks like the server's time is off. If you have SSH access, does >> > running date give you the correct time? >> >> > On 20/10/2010, at 5:42 PM, Super Steve wrote: >> >> > > I host a website on iServe that uses date() and time() to do some date >> > > arithmetic and I found I was getting different results on my local >> > > machine (Windows XP running Apache and PHP 5.2.10) and the iServe >> > > server (PHP 5.2.9). >> >> > > To try to do some trouble shooting I wrote a little script that >> > > outputs some values and I found that the iServe server seems to be >> > > running an hour slow. >> >> > > Here's my script: >> >> > > <?php >> > > echo "<p>" . time() . "</p>"; >> > > echo "<p>" . date("d F Y H:i:s") . "</p>"; >> > > echo "<p>" . date("c") . "</p>"; >> > > echo "<p>" . date("r") . "</p>"; >> > > echo "<p>" . date("I O T Z") . "</p>"; >> > > ?> >> >> > > Running this on my local machine, at 5:30PM on October 20th I get the >> > > following results: >> >> > > 1287549026 >> > > 20 October 2010 17:30:26 >> > > 2010-10-20T17:30:26+13:00 >> > > Wed, 20 Oct 2010 17:30:26 +1300 >> > > 1 +1300 NZDT 46800 >> >> > > Running on the iServe server that hosts my website I get the following >> > > results: >> >> > > 1287545413 >> > > 20 October 2010 16:30:13 >> > > 2010-10-20T16:30:13+13:00 >> > > Wed, 20 Oct 2010 16:30:13 +1300 >> > > 1 +1300 NZDT 46800 >> >> > > There may have been just a few seconds difference between when I ran >> > > the script on each machine, and of course I expect the time to be out >> > > by several seconds. >> >> > > But if I'm reading this correctly, iServe is reporting that the >> > > current time is 4:30pm when it's really 5:30pm. >> >> > > Am I understanding this correctly (in which case I should notify >> > > iServe) or do I not understand the subtleties of PHP's date() and >> > > time() and daylight savings? >> >> > > -- >> > > NZ PHP Users Group:http://groups.google.com/group/nzphpug >> > > To post, send email to [email protected] >> > > To unsubscribe, send email to >> > > [email protected] >> >> > --- >> > Simon Welsh >> > Admin ofhttp://simon.geek.nz/ >> >> > Who said Microsoft never created a bug-free program? The blue screen >> > never, ever crashes! >> >> >http://www.thinkgeek.com/brain/gimme.cgi?wid=81d520e5e > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] > -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
