After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 140800 - Return value of FAMMonitorDirectory() and FAMMonitorFile() is not checked
Return value of FAMMonitorDirectory() and FAMMonitorFile() is not checked
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Module: file
cvs (head)
Other Linux
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks: 140095
 
 
Reported: 2004-04-22 01:14 UTC by Federico Mena Quintero
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Federico Mena Quintero 2004-04-22 01:14:23 UTC 
See file-method.c:2325.  What does FAM return if the directory does not exist in
the first place?
Comment 1 Federico Mena Quintero 2004-04-22 01:16:44 UTC 
If FAM does return an error in this case, and if gnome-vfs checked it, it would
mean that a cleaner solution for bug #140095 is possible --- for now I added a
gnome_vfs_uri_exists() check to GtkFileSystemGnomeVFS, but that should not be
needed.
Comment 2 Alexander Larsson 2004-05-04 13:42:28 UTC 
Monitoring a non existing file/directory is not an error with fam. You'll just
not get an EXISTING event, but you'll get told later when/if the directory shows up.
Comment 3 Federico Mena Quintero 2004-05-06 14:38:22 UTC 
Still, shouldn't we do something sensible if those calls return an error?
Comment 4 Federico Mena Quintero 2004-07-21 02:31:45 UTC 
I've checked the FAM sources and those calls don't ever return errors.  Sigh. 
I'll do something different for the file chooser backend, then.