Re: Missing specific FSEvents after restart
Re: Missing specific FSEvents after restart
- Subject: Re: Missing specific FSEvents after restart
- From: Dominic Giampaolo <email@hidden>
- Date: Tue, 14 Sep 2010 12:37:59 -0700
> Before I file a bug report, I wanted to run this problem past the list. I'm also trying to figure out if this is an OS X issue or a VMWare issue.
>
If what I think is happening is in fact happening then
it's a tricky issue.
We've seen cases where this occurs because the process
making changes to the files exits *after* fseventsd exits
and so fseventsd never sees the change. In the case of
VMware, although they may have exited the VM there are
still background processes that may continue to update
state (I know this is true with Parallels and I expect
it to be the same with VMware).
It would be interesting to get the output of:
sudo ls -lT /.fseventsd
and then "ls -lT" on the files that should have been
reported as modified but were not.
I'd also need to see the timestamp on when the system
was rebooted (which should be in /var/log/system.log).
If the files were modified after fseventsd exited, then
it's hard for us to do much about that. The fseventsd
process is supposed to be one of the last things that
exits before the system reboots. However we don't have
control over third party apps/daemons/code and so there
is no way to enforce it.
--dominic
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden