| From | "David Newman" <DNewman at synacor dot com> |
| Subject | Imapsync output question |
| Date | Fri, 5 Dec 2008 16:02:27 -0500 |
|
I’ve recently tested ImapSync with great success. I’m
very impressed with this script. I’ve built a wrapper perl script that calls imapsync
then processes prefs, contacts and filters. One small issue I’ve noticed is that when I call
imapsync from within my perl script, I’m redirecting the output to a file
with the “>>” So for example: Imapsync [flag, flag, flag] >> output.log When I run my script which runs for 2 hours, on the average it
transfers 90 gig of data. Imapsync does a wonderful job in migrating the email. Most of the log files produced are complete with all output expected.
There are a number of times the log files are not complete. Some of the log files stop in the middle of printing a
folder and it’s email. I’m forking 50 connection of imapsync at a time. I
believe this is a buffering issue but how would I resolve this issue if the
buffering is actually from imapsync itself. How would I flush imapsyncs print buffer? Thanks. David Newman |