tty device timestamps are not meaningful #545
Comments
The answer to that question appears to be look for "Microsoft" in the output of /proc/version. But that doesn't appear in the output of |
|
I'd suggest using /proc/sys/kernel/osrelease which will be "3.4.0-Microsoft" I didn't see anything Microsoft-specific in any of the uname -a output. I'll take a look at why the tty stat call is always returning the current time. |
floam
added a commit
to fish-shell/fish-shell
that referenced
this issue
Jun 25, 2016
microsoft/WSL#545 Just looking for "Mirosoft" is rather general - we don't want to enforce this strange behavior for Windows 12 (or the next beta.)
floam
added a commit
to floam/fish-shell
that referenced
this issue
Jul 4, 2016
microsoft/WSL#545 Just looking for "Mirosoft" is rather general - we don't want to enforce this strange behavior for Windows 12 (or the next beta.)
|
Build 15032 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was interested in solving a problem with the fish shell so I did some debugging. It appears that the timestamps in the
struct statreturned byfstat(1,...)are always the current time. Both on Cygwin and WSL. The workaround for Cygwin is to disable the check of those timestamps based on the definition of macros such as_WIN32. Those conditional checks don't work on WSL.How can I test, at compile time, that the program is targeted for WSL? If that isn't possible how do I test at run time that the program is running under WSL?
The text was updated successfully, but these errors were encountered: