>>>>> On Sun, 4 Dec 2005 17:49:47 -0500, Frank Sweetser <[EMAIL PROTECTED]> >>>>> said:
Frank> I upgraded recently to 1.38.2 and while everything appears to be functioning Frank> normally, I've noticed some odd behavior from the file daemon and director. Frank> When the storage daemon hits the maximum spool size limit and starts writing Frank> the data out to tape, both the file and director daemons end up spinning at Frank> 100% cpu utilization until the storage daemon is finished and either ends the Frank> job or goes back to spooling more data. I've seen this behavior on both redhat Frank> 9 and fedora core 4 systems. I tried stracing it, but strace just shows it as Frank> waiting in select(), so I assume that strace isn't picking the thread that's Frank> doing the work. Have you tried strace with the -f option? In FC3 at least, this traces all threads. __Martin ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
