On Fri, Jul 13, 2007 at 12:48:14PM +0100, Mac wrote: > > James R Grinter wrote:- > > > >On Fri, Jul 13, 2007 at 09:39:37AM +0100, Mac wrote: > >> On one previous occasion, the whole thing seemed to grind to a virtual > >> halt, and we suspected (but couldn't prove) that a locking battle over > >> (something like) secrets.tdb was to blame. > > > >(I recognise that symptom, see below) > > > >> Something that stands out is a huge ammount of time (1.9 - 2.0 seconds) > >> spent reading a file in /var/tmp (/var/tmp/firesun1_044_0). This seems > >> to happen quite often (maybe every few seconds). This file isn't terribly > >> (human) readable, and I don't recall Samba ever having needed > >> a temp file outside of 'var/locks'. > > > >that's not one I recognise. > > Closer inspection of the 'truss' output reveals that each process, > having 'read' its way through the entire file, then writes 81 (ish) > bytes out to the end of the file. These bytes look a bit like a machine > trust account name. > > Here's an extract from the 'truss' output. > > write(29, "\0\0\018 g k m t x 2 j $".., 81) = 81 > fdsync(29, O_RDONLY|O_SYNC) = 0 > > Repeated 'ls -l' of the file in /var/tmp reveals that it both shrinks and > grows over time.
Looks like this might be a utmp record to me (maybe libc trying to create one) ? Have you tried compiling with utmp turned off ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
