samba - Feb 2001 - *HUGE* connections.tdb w/ 2.2.0a2

I've notice that after somewhere between 4 and 12 hours of operation,
connections.tdb becomes insanely huge: by this I mean about 1GB in size.
I think the only reason the file stopped there was that the disk was
full. I'm certain it's not a high load issue: this machine is only 
handling 16 clients... needless to say, the only way to work around this
it seems is to kill the daemon and nuke connections.tdb. help?

Also, would anyone have a suggestion on where to go about diagnosing an
odd printing problem? The users can mount/read/write their home dirs, some
can print, some cannot. I turned up the debug level and noticed a number
of calls for "getpwnam(ADMINISTRATOR)" , "getpwnam(printer
admins)" and
the like... help?

Samba 2.2.0-alpha2
HP/UX 10.20

-- 
Chris Kuethe:  System Administrator  -   U of A Math Dept.

cell: 780.903.9475                    office: CAB553, 780.492.1704    
wargames@{edmc.net,hackcanada.com}    ckuethe@[[gecko.]math.]ualberta.ca

Opinions expressed herein are solely the responsibility of
the author. And the author wouldn't have it any other way.

root writes:
> I've notice that after somewhere between 4 and 12 hours of operation,
> connections.tdb becomes insanely huge: by this I mean about 1GB in size.
> I think the only reason the file stopped there was that the disk was
> full. I'm certain it's not a high load issue: this machine is only 
> handling 16 clients... needless to say, the only way to work around this
> it seems is to kill the daemon and nuke connections.tdb. help?
Can you tell me whether this file is sparse, or actually that big?

You might want to repost this to samba-technical, as someone
there might be able to help you.


Regards,

Tim.