github.com/glinton/ctime
Ctime is meant to be a linux only inode event trigger. It will update the ctime only (to current time), allowing listeners to be notified, but not break certain text editors where the file may be open. ctime's results are similar to `touch -cr file file` where no new file is created, and the atime and mtime remain "unmodified." Running is as simple as specifying a single file: Multiple files may also be specified:
Readme
Ctime is meant to be a linux only inode event trigger. It will update the ctime only (to current time), allowing listeners to be notified, but not break certain text editors where the file may be open.
ctime's results are similar to touch -cr file file where no new file is created, and the atime and mtime remain "unmodified."
Running is as simple as specifying a single file:
ctime /path/to/file
Multiple files may also be specified:
ctime file1 file2 file3 file4
FAQs
Ctime is meant to be a linux only inode event trigger. It will update the ctime only (to current time), allowing listeners to be notified, but not break certain text editors where the file may be open. ctime's results are similar to `touch -cr file file` where no new file is created, and the atime and mtime remain "unmodified." Running is as simple as specifying a single file: Multiple files may also be specified:
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A new report explores how advancements in LLMs are enhancing cyber threats, including polymorphic malware, personalized spearphishing, and the risk of hijacking customer service bots.
Security News
ESLint has approved an RFC that adds support for TypeScript configuration files, which is aimed at improving the developer experience and recognizing changes in the evolving JavaScript ecosystem.
Security News
The NVD is facing a significant backlog with over 12,500 CVEs awaiting analysis, and more than 50% of known exploited vulnerabilities (KEVs) left unenriched since mid-February.