generic/236 test failure (failure to update ctime on hardlink) turned out not to be a client issue

[Steve French]

Was having problems reproducing the generic/236 ("Check ctime updated
or not if file linked") failure that we saw on the buildbot to Windows
(e.g. http://smb311-linux-testing.southcentralus.cloudapp.azure.com/#/builders/6/builds/67/steps/91/logs/stdio)
but then found out that the issue was the clock was off on the test
server VM.  When I reset the time in the Windows server VM properly
the test now passes in our 'buildbot.'

The test (generic/236) still fails to Samba server but that is a
server bug (Samba server reads ctime from mtime so you don't see ctime
updated on hardlinks as expected), but at least this test works to
Windows server, ksmbd server etc, and have confirmed that it is not a
Linux client issue.

-- 
Thanks,

Steve