[Interest] Interval QTimer not firing in server after running for months

[Jason H]

How do you know it didn't try to grab an incomplete file, fail, and mark itself as updated?

One nicety of the FS watcher is you only get notification on close() of the file.  I don't know why it didn't work for you, it has always worked for me.





________________________________
 From: Karl Ruetz <karl.ruetz at ruetzdogz.com>
To: tony at rightsoft.com.au; interest at qt-project.org 
Sent: Monday, January 14, 2013 9:19 AM
Subject: Re: [Interest] Interval QTimer not firing in server after running for months
 

I have a server product that runs four daemons that have similar algorithms.   They have run for months with no problem. 

Karl


Sent from my Galaxy S®III


-------- Original message --------
From: Tony Rietwyk <tony at rightsoft.com.au> 
Date: 
To: interest at qt-project.org 
Subject: [Interest] Interval QTimer not firing in server after running for
 	months 


Hi Everybody, 

My Qt server runs on machines in the cloud with Debian 'squeeze' and Qt
4.6.3.   It needs to respond to changes in its configuration settings file.
Since QFileSystemWatcher didn't work, my code just polls every 10 minutes
using QTimer.   It has been running since 10 Oct last year.  A recent config
change was not picked up by the server.  

Are there any known problems with QTimer running for months on end -
especially in that Qt version?  

Thanks! 

Tony


_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20130114/425aac35/attachment.html>