git-fsmonitor—​daemon - A Built-in File System Monitor


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 file system notification facilities.

This daemon communicates directly with commands like git status using the simple IPC interface instead of the slower githooks[5] interface.

This daemon is built into Git so that no third-party tools are required.



Starts a daemon in the background.


Runs a daemon in the foreground.


Stops the daemon running in the current working directory, if present.


Exits with zero status if a daemon is watching the current working directory.


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.

When core.fsmonitor is set to true (see git-config[1]) 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[1].


The fsmonitor daemon does not currently know about submodules and does not know to filter out file system 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.

© 2012–2022 Scott Chacon and others
Licensed under the MIT License.