Member copyRequest::base::printResults (std::ostream &hashStream, std::ostream &logStream)

to little structure, unreadable code

was follow before, ugly condition

When an anonymous tmp file is created and made visible via open(dirpath, O_WRONLY|O_TMPFILE);inkat(AT_FDCWD, "/proc/self/fd/%fd", AT_FDCWD, path, AT_SYMLINK_FOLLOW) no CLOSE_WRITE event is triggered. Not likely to happen as SL7/Centos7's kernel does not support O_TMPFILE, and also NFS does not support it (apparently)

When a file in a watched directory has a hard link from an unwatched directory and is modified using that other link no notification is produced.

Member outputHandler::daosFs::rename (const std::string &fromPath, const std::unique_ptr< const genericStat > &readInitialStat, const std::string &toPath, copyRequest::stateType &state) override

what if at the end a directory is renamed?

Member outputHandler::dcap::rename (const std::string &fromPath, const std::unique_ptr< const genericStat > &readInitialStat, const std::string &toPath, copyRequest::stateType &state) override

what if at the end a directory is renamed?

Member outputHandler::libssh::rename (const std::string &fromPath, const std::unique_ptr< const genericStat > &readInitialStat, const std::string &toPath, copyRequest::stateType &state) override

what if at the end a directory is renamed?

Member outputHandler::posixFile::rename (const std::string &fromPath, const std::unique_ptr< const genericStat > &readInitialStat, const std::string &toPath, copyRequest::stateType &state) override

what if at the end a directory is renamed?