From: Bán M. <ba...@vo...> - 2010-09-08 20:33:12
|
Hi, Sorry, I was wrong. The version no is 1.6.17. I've patched the mfsmetalogger/masterconn.c file with the following lines: 140a141 > 187a189,192 > if (eptr->logfd) { > fclose(eptr->logfd); > eptr->logfd = NULL; > } which have solved that problem. So this is the bug fix. There was no fclose after opening the changelog_ml.0.mfs. Miklos On Wed, 8 Sep 2010 14:33:39 -0400 Travis Hein <tra...@tr...> wrote: > > On 2010-09-06, at 10:16 AM, Bán Miklós wrote: > > >> > >> Metaloggers should continuously receive the current changes from > >> the master server and write them into its own text change logs > >> named changelog_ml.0.mfs. > >> > >> How do you know that in your system they are save hourly? Don't > >> they increment with every change in the filesystem? > > > > Yes, exactly. There is no new lines on metalogger server's > > changelog_ml.0.mfs, while the master's changelog.0.mfs updating. > > Nevertheless the sessions_ml.mfs is updating continuously. > > My server version is 1.6.7 and it is running on Ubuntu Jaunty. > > > > Did you mean 1.6.17 ?,, or 1.5.7. (There was no 1.6.7 release?) > > I was concerned, if you were not running the latest server and > metalogger, perhaps this would be a bug that has already been fixed. > > Travis > > > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > moosefs-users mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moosefs-users |