Am Donnerstag, den 25.08.2005, 20:28 +0100 schrieb Nick Lunt: > Hello folks, > > I have the following code taken from the Twisted examples - > > [code] > # filewatcher.py > from twisted.application import internet > > def watch(fp): > fp.seek(fp.tell()) > for line in fp.readlines(): > sys.stdout.write(line) > > import sys > from twisted.internet import reactor > s = internet.TimerService(1.0, watch, file(sys.argv[1])) s = [internet.TimerService(1.0, watch, file(x) for x in sys.argv[1:]] for x in s: x.startService() > s.startService() > reactor.run() > s.stopService() > [/code] > > I find this piece of code amazing and I am keen to put it to use. > If I run './filewatcher.py myfile' it will print out any changes made to > 'myfile', very similar to 'tail -f' . > > Now if I want to have this program monitor several files at once I could > run './filewatcher.py file1 file2 filex' or './filewatcher.py file1 & > ./filewatcher file2 & etc' both with minor modifications to the code, Well, compared to threads, executing a stat and/or read (I guess it goes the read way, which is interesting, usually one watches files by doing stat) is not relevant. > but I think that could cause performance problems relating to the OS. > So I'm thinking I will need to learn python threads (no bad thing) How would adding Threads to the mix solve any performance problems *g*
Andreas
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
