> "logical" == logical american writes:
logical> That is the $64,000 question, I want to know why the gcc
logical> compiler changed the timezone to LMT on its own.
I'm guessing it's an artifact of glibc's mktime() implementation. I'd
suggest looking that the
> "Russell" == Russell Senior writes:
> "logical" == logical american writes:
logical> That is the $64,000 question, I want to know why the gcc
logical> compiler changed the timezone to LMT on its own.
Russell> I'm guessing it's an
It appears to be garbage in - garbage out, via a very obscure route.
If you start off with
TZ=PST8PDT
export TZ
call your program
then you get consistent results, with the tm_zone portion of the struct
set to PDT in both cases.
the man page for mktime doesn't indicate that the tm_gmtoff and
Steve:
Same result, so it's not the TZ environmental variable.
#include
#include
#include
#include
int main() {
char pacific_timezone[8] = "PST8PDT";
char * timezone =_timezone[0];
// Date: November 18, 1883 12:07:01 am PST
struct tm first_tm;
One more important thing which I wish to point out, the problem with the
12:07:01 pm November 18, 1883 time is NOT occurring with the date
command from the command line prompt. I would have thought that date
and mktime would match, in their results for any selected date. But
apparently they
On Mon, 25 Jan 2016, King Beowulf wrote:
> This will depend on whether you are going for screen (web) or printer
> output, dpi required, and the pdf contents (embedded ps text or compressed
> jpg images) and original pdf data source. IIRC, ghostscipt may deal with
> ps based pdf files better,
Good, there are a boat load of options out there. The MotionPi thing is
interesting
but I would rather use separate cameras and use the Pi as the DVR.
I have not used Motion, I have read a bit about it, but ZM did a lot more
and
fit my needs so that is what I was using.
On Tue, Jan 26, 2016 at
> galens@lion:~$ make mktime_test
> cc mktime_test.c -o mktime_test
> galens@lion:~$ ./mktime_test
> first struct tm object dump: 1 7 12 18 10 -17 0 321 0 -28378 LMT
> second struct tm object dump: 2 7 12 18 10 -17 0 321 0 -28800 PST
> First time tick: -2717640001 Second time tick:
On 1/26/2016 4:49 AM, David Barr wrote:
> I will quite happily play the straight man, here: why are `gmtoff` and `zone`
> different in `first_tm` vs `second_tm`?
>
> David
That is the $64,000 question, I want to know why the gcc compiler
changed the timezone to LMT on its own.
Thanks, Chuck. I spent a few hours reading & watching videos about
Zoneminder. Lots of interesting potential. Also found this (not
ZoneMinder) "http://pimylifeup.com/raspberry-pi-security-camera/;
On Mon, Jan 25, 2016 at 9:18 PM, Chuck Hast wrote:
> Google the following:
>
I will quite happily play the straight man, here: why are `gmtoff` and `zone`
different in `first_tm` vs `second_tm`?
David
> On Jan 25, 2016, at 20:57, Galen Seitz wrote:
>
> On 01/25/16 17:23, logical american wrote:
>> To C geeks:
>>
>> Could someone who has
11 matches
Mail list logo