Anything off about the \tmp parition on our test machine?

[Cantor, Scott]

On 2/11/15, 11:18 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:


>
>It all comes down to the fact that the file I'm looking at in the service
>test, which lives of \tmp returns a lastModified() date of 0, which spring
>then misreads as "File doesn't exist" - even though it does because we
>predicate our query to spring on that.

Well, I don't know if the partition is responsible, but what I see is:

-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest1829314008617520401.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest2162301248094443344.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest3212250646365060870.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest4177539096220920298.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest6735548727510973416.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest7358103548410698044.xml
-rw-r--r--  1 jenkins    jenkins        600 Dec 31  1969 
ReloadableSpringServiceTest7471602029381402229.xml

That seems a bit weird, and IIRC, that's the last instant before the 
32-bit epoch? Which would suggest an overflow.


-- Scott