Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trace readdir #12

Open
droundy opened this issue May 22, 2016 · 2 comments
Open

trace readdir #12

droundy opened this issue May 22, 2016 · 2 comments

Comments

@droundy
Copy link

droundy commented May 22, 2016

For fac/bigbro, readdir is an important operation to trace. It's needed if you have a build rule such as:

echo *.c > file.dat

in which case the rule needs to be rebuilt if a new file is created in that directory.

@jacereda
Copy link
Owner

Would it require a separate operation type or is a 'read' of the directory enough?

@droundy
Copy link
Author

droundy commented May 23, 2016

Different system calls are used for reading directories. I would output it
as a separate type as well (and do so), since tools might want to ignore
changes to directories, and it saves effort to treat them as distinct, to
avoid the need for the caller to stat each reported read.

On Mon, May 23, 2016 at 11:21 AM jacereda [email protected] wrote:

Would it require a separate operation type or is a 'read' of the directory
enough?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#12 (comment)

@ndmitchell ndmitchell mentioned this issue May 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants