RE: [PATCH] fsmonitor: option to allow fsmonitor to run against network-mounted repos

From: Eric DeCosta <edecosta@mathworks.com>
Date: Aug 24, 2022, 15:45 UTC
Message-ID: <BL0PR05MB55716C6CC59D3258E55B25B9D9739@BL0PR05MB5571.namprd05.prod.outlook.com>
In-Reply-To: <055470ae-1483-bbd4-5b23-3762a4c131b8@jeffhostetler.com>

Show 9 quoted lines

> I would also set GIT_TRACE_FSMONITOR and GIT_TRACE2_PERF (on both daemon
> and client sides of the tests) and capture the logs and try to figure
> out what is happening.
>
> I suspect that this testing should wait until you redo the patch to
> remove the tmp file stuff and just move the socket into $HOME as we
> talked about earlier.
>
> Jeff

All tests are passing now with the new patch. By default the socket is written into the original location (.git directory) unless 'fsmonitor.allowRemote' is true. Only then is $HOME used and if $HOME proves unsuitable the user can override that by setting 'fsmonitor.sockerDir' to some valid, local directory.

-Eric