On Tue, Apr 05, 2005 at 11:53:01AM -0400, Matt Swift wrote: > >> "S" == Steve wrote:
> S> Matt,
> S> On Mon, Apr 04, 2005 at 09:33:07PM -0700, Debian Bug Tracking System
> wrote:
> >> Processing commands for [EMAIL PROTECTED]:
> >> > reopen 274969
> >> Bug#274969: smbd consumes available CPU cycles
> >> Bug#286818: /var/run/samba/messages.tdb growing up indefinitely
> >> Bug#295256: samba: hangs on printing
> >> Bug reopened, originator not changed.
> S> Can you elaborate? Can you check the size of the printer .tdb files in
> S> /var/cache/samba/printing/, and delete any grossly oversized ones? My
> S> suspicion is that this bug is fixed, but that the already-corrupted
> tdb on
> S> your system is still causing problems; sorry for not being more
> explicit
> S> about this.
> Are these files large?
Indeed not; these are typically sized cache files.
> Can I simply delete all these .tdb files while samba is not running
> and they will be recreated when samba restarts?
Yes, they should be recreated without problem if you delete them; I don't
currently see any reason to think that will help in your case, but it
shouldn't hurt to try.
The other thing you might want to do, though, is
find /var/run/samba/ /var/cache/samba/ /var/lib/samba -name '*.tdb' \
-size +1024k
and see if there are any other extremely large tdb files on your system --
the other one that was mentioned in one of the reports as getting corrupted
was /var/run/samba/messages.tdb. Do *not* delete any files from
/var/lib/samba/, as they are not going to be regenerated for you.
> One oddity that has been there for a while is that the printer
> exported by samba shows up on the Windows XP clients as having 153
> documents in the queue (I recall 149 as well), even though there are
> none when I check on the samba machine with lpq, and indeed when I
> look at the print queue from Windows there is nothing in it.
Hmm, maybe that points to a problem in /var/cache/samba/printing/ after
all...
> This seems to indicate just about 14% use, and it gives the same
> numbers or very close each time I run ps.
> Top and gtop, on the other hand, report numbers consistently in the
> 80-90% range, fluctuating, and sometimes dipping lower.
> What's the most helpful way to measure this?
Telling me whether the current behavior is causing you problems ;)
Cheers,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
