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 167898 - gamin reports monitored files > 2GB to be deleted
gamin reports monitored files > 2GB to be deleted
Status: RESOLVED FIXED
Product: gamin
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Gamin Maintainer(s)
Gamin Maintainer(s)
: 302013 304973 309388 311213 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-02-19 18:32 UTC by Martin Wehner
Modified: 2005-07-22 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin Wehner 2005-02-19 18:32:24 UTC 
Version details: gamin-0.0.24-1.FC3
Distribution/Version: FC3/kernel-2.6.10-1.766_FC3

When you monitor a file > 2GB with gamin, you get a FAMDeleted event immidiately
after installing the monitor.

$ dd if=/dev/zero of=bigfile bs=16k count=131073
$ testgam
> connect
connected
> monfile bigfile
monfile bigfile 0
>
1: bigfile Deleted: NULL
1: bigfile EndExist: NULL
>

This e.g. leads nautilus to believe the file disappeared when you try to open
the properties for such a file.
Comment 1 Martin Wehner 2005-05-02 20:14:51 UTC 
*** Bug 302013 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Veillard 2005-05-09 13:46:54 UTC 
  Okay, reproduced and fixed in CVS (compiling with big file support was
sufficient.
  I added a regression test for it so it will show up in case
of regressions.

  Thanks a lot for the report !

Daniel
Comment 3 Martin Wehner 2005-05-10 18:32:41 UTC 
Great, thanks!
Comment 4 Martin Wehner 2005-05-21 13:18:43 UTC 
*** Bug 304973 has been marked as a duplicate of this bug. ***
Comment 5 Olav Vitters 2005-07-04 20:42:51 UTC 
*** Bug 309388 has been marked as a duplicate of this bug. ***
Comment 6 Teppo Turtiainen 2005-07-22 15:40:19 UTC 
*** Bug 311213 has been marked as a duplicate of this bug. ***