QFileSystemWatcher not working with /etc/mtab
I’ll try to be brief:
My program should automatically sense when a USB device is plugged and also where that device was mounted. So far I’ve been able to sense the usb device plugged, as well as getting which device was inserted (i.e. /dev/sdc1).
Knowing the device (i.e. /dev/sdc1) I can then simply look inside /etc/mtab to match that device with its mount point (i.e. /media/USBDRIVE). However when I try to find that device inside /etc/mtab, I get nothing, but if I tell the program to wait 1 second before trying to search inside /etc/mtab, it works, meaning my program was actually trying to find the device before it was actually added to /etc/mtab
So what I did was instead of waiting 1 second to search in /etc/mtab, I created a QFileSystemWatcher for that file:
But watcher never detects any change in /etc/mtab! Even if try /proc/mounts which is the same file… What is weird is that for any file inside /home, QFileSystemWatcher will work, but for /etc or /proc files it won’t work.
I will thank you guys for any help, since the 1 second wait is not the best approach..
Judging from this [qt.gitorious.org] patch applied to Qt Mobility, there is a bug in QFileSystemWatcher, preventing it from being used in /etc/mtab. Maybe the patch I liked to can help you, too.
loladiro: I read that page before, but I didn’t quite understood what was going on…
peppe: I don’t know what would be to return to the event loop, but my guess is that my code is correct, otherwise it wouldn’t work with files inside /home directory right?
If I change “/etc/mtab” to say a file in my home folder, the fileChanged signal is emitted, but not for “etc/mtab” file :(
The patch to Qt Mobility I linked basically changes the QFilesSystemWatcher and uses its inotify backend for linux. I think it is pretty straight forward what is going on, and since it does exactly what you want (listening for new devices), it might be worth it for you to see what’s going on and how they replaced the old QFileSystemWatcher syntax (in red) with inotify (in green).
excuse me friend because of my low english writing ability
i think that you want check your USB devices, and for doing it, you watch a file usign filewatcher that OS change it when a new usb connect or disconnect, but your watch doesn’t work and does not determine any change in file.
now you want understand why this problem occured? YES?