Shell doesn't get local time? Is this new?

[vibroverbus]

Not sure if this is a new thing or not, I think it is, but just noticed my shell sessions were in UTC. No TZ env variable being exported. I added that to jffs/configs/profile.add and seems to work fine now but... is that new? Or did I just never notice?

All other system dates are churning along fine including everything in the system log (unless I was generating an entry from an interactive shell session)...

Just wondering.

 

[ColinTaylor]

I've seen this reported from time to time (no pun intended ). What hardware/firmware are you using?

John's firmware added the TZ entry to release/src/router/rom/rom/etc/profile back in 2016 but I don't think @RMerlin did the same.

 

[thelonelycoder]

Not sure if this is a new thing or not, I think it is, but just noticed my shell sessions were in UTC. No TZ env variable being exported. I added that to jffs/configs/profile.add and seems to work fine now but... is that new? Or did I just never notice?

All other system dates are churning along fine including everything in the system log (unless I was generating an entry from an interactive shell session)...

Just wondering.

What firmware and router model is this on?

 

[vibroverbus]

AC3200 & 384.3

Everything else works brilliantly, and as I say, profile.add fixes it right up (gave me opportunity to add a fancier prompt too, like newer DD-WRT releases use...)

 

[thelonelycoder]

AC3200 & 384.3

Everything else works brilliantly, and as I say, profile.add fixes it right up (gave me opportunity to add a fancier prompt too, like newer DD-WRT releases use...)

The date is correct, just the TZ is wrong?
I can't help, I'm more interested what the shell reports vs the actual UI for my scripts for those seldom cases it is not applied to it.

 

[vibroverbus]

Yep. No TZ was being set in default profile, so it reports a perfectly correct UST. Unfortunately that was being used for log entries so any shell scripts I was running would be stamping syslog entries with 'dates in the future', while all the system log entries looked fine.