Linux clock function, signed or unsigned?

[Valhalla_Guy]

Just wondering if anyone running a validator has switched to unsigned integers for the Linux clock value. I was told many months ago this was (recommended) happening. Is it in the latest release, or is this simply a choice made by each each validator, when nodes are first setup?

I assume you already know why I am asking, I am looking for confirmation that it is truly a no brainer, with no hidden adverse effects. 

My guess is that other internal variables will need to be reconfigured as well, to prevent an overflow.