Am 15.03.2011 08:51, schrieb Ralf Gross: > Christian Manal schrieb: >> Thanks for the pointer. From Solaris 10 malloc(3C): >> >> [...] After free() >> is executed, this space is made available for further allo- >> cation by the application, though not returned to the sys- >> tem. Memory is returned to the system only upon termination >> of the application. [...] >> >> So I have to restart Bacula after everything is done to get the memory >> back. That kinda sucks and is clearly not Bacula's fault. > > > you may want to take a look at 2 recent bug reports: > > 0001686: Memory Bacula-fd is not released after completed backup > 0001690: memory leak in bacula-fd (with accurate=yes) > > http://bugs.bacula.org/ > > Ralf
Thanks, but they don't seem to be relevant in this case. Both bugs are reported for Linux and seem to be related to Linux' memory management. Since I'm using Solaris I don't think this applies to me. Also, after several accurate jobs running without restarting Bacula, the total memory usage of the director and fd didn't go up anymore, so I presume it comes down to the behavior of Solaris' free(), as described in the above quoted manpage. Regards, Christian Manal ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
