Subj : Squish __ftsc_date bug / JAM bug
To   : andrew clarke
From : Oli
Date : Mon Feb 15 2021 15:23:21

andrew wrote (2021-02-16):

 ac> It's been so long since I used the original SquishMail (ie. squish.exe)
 ac> that I don't recall if rescans were a supported feature.

 ac> ("squish.exe rescan 3:633/267 fidosoft.husky" maybe?)

SQUISH RESCAN <area_tag> <node>

 ac>>> The JAM spec says:

 ac>>> "An ulong representing the number of seconds since midnight,
 ac>>> January 1, 1970."

 ac>>> Presumably that's 1970-01-01 00:00 UTC, not local time.

 Ol>> I don't think it's meant to be UTC. From the JAM spec:
[...]
 ac> You could be right, but at the very least it's ambiguous since AFAIK the
 ac> convention is for time_t on Linux/BSD be stored as UTC.

especially if it's called "UNIX date" in the spec. If it's not a real UNIX time stamp (which is always in UTC), what is it then? And what is the exact meaning of "the number of seconds since midnight, January 1, 1970" when UNIX time is "the number of seconds that have elapsed since the Unix epoch, minus leap seconds"? ;-P

---
 * Origin: . (2:280/464.47)

.