Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.39.1 → 2.40.0 no changes
- 2.39.0 12/12/22
git fsmonitor--daemon start git fsmonitor--daemon run git fsmonitor--daemon stop git fsmonitor--daemon status
A daemon to watch the working directory for file and directory changes using platform-specific filesystem notification facilities.
This daemon communicates directly with commands like
using the simple IPC interface
instead of the slower githooks interface.
This daemon is built into Git so that no third-party tools are required.
This daemon is a long running process used to watch a single working
directory and maintain a list of the recently changed files and
directories. Performance of commands such as
git status can be
increased if they just ask for a summary of changes to the working
directory and can avoid scanning the disk.
core.fsmonitor is set to
true (see git-config)
commands, such as
git status, will ask the daemon for changes and
automatically start it (if necessary).
For more information see the "File System Monitor" section in git-update-index.
The fsmonitor daemon does not currently know about submodules and does not know to filter out filesystem events that happen within a submodule. If fsmonitor daemon is watching a super repo and a file is modified within the working directory of a submodule, it will report the change (as happening against the super repo). However, the client will properly ignore these extra events, so performance may be affected but it will not cause an incorrect result.
By default, the fsmonitor daemon refuses to work against network-mounted
repositories; this may be overridden by setting
true. Note, however, that the fsmonitor daemon is not guaranteed to work
correctly with all network-mounted repositories and such use is considered
On Mac OS, the inter-process communication (IPC) between various Git commands and the fsmonitor daemon is done via a Unix domain socket (UDS) — a special type of file — which is supported by native Mac OS filesystems, but not on network-mounted filesystems, NTFS, or FAT32. Other filesystems may or may not have the needed support; the fsmonitor daemon is not guaranteed to work with these filesystems and such use is considered experimental.
By default, the socket is created in the
.git directory, however, if the
.git directory is on a network-mounted filesystem, it will be instead be
$HOME itself is on a
network-mounted filesystem in which case you must set the configuration
fsmonitor.socketDir to the path of a directory on a Mac OS native
filesystem in which to create the socket file.
If none of the above directories (
is on a native Mac OS file filesystem the fsmonitor daemon will report an
error that will cause the daemon and the currently running command to exit.
Everything below this line in this section is selectively included from the git-config documentation. The content is the same as what’s found there:
By default, the fsmonitor daemon refuses to work against network-mounted repositories. Setting
trueoverrides this behavior. Only respected when
core.fsmonitoris set to
This Mac OS-specific option, if set, specifies the directory in which to create the Unix domain socket used for communication between the fsmonitor daemon and various Git commands. The directory must reside on a native Mac OS filesystem. Only respected when
core.fsmonitoris set to
Part of the git suite