>>>>> On Fri, 24 Aug 2007 11:21:28 -0400, Steve Campbell said: > > I still have quite a few servers running the 2.4 kernel. All of these > are Red Hat clone machines. I do not feel comfortable removing or > renaming the library, so I have a few questions.I am just getting > started with Bacula, BTW. > > What module uses this that causes the problem? Is it safe to leave the > library in tact on clients? In other words, Is it the director, storage > director, file director, or some combination of them that requires this > to be eliminated?
All the Bacula daemons are affected by the tls bugs. They will not run reliably with the tls library in memory, but it is safe to leave the library on disk. > In the event that it is all of them, or at least the file director, and > I have to do something with my client-only machines, can someone tell me > exactly how I would set up the workaround mentioned in the manual > (loader environment variable LD ASSUME KERNEL=2.4.19 ). You need a line like this in the scripts that start the daemons: export LD_ASSUME_KERNEL=2.4.19 It is possible that the scripts already do this. You can check which libc a daemon is using by doing cat /proc/$pid/maps where $pid is the pid of the daemon. __Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
