search for: tdb_file

[apologies to the samba list if you aren't interested in this] I've rewritten the TDB perl bindings from scratch. this version: * is on CPAN (http://search.cpan.org/search?mode=module&query=TDB_File) * supports 8-bit keys and values * gives access to the complete TDB API Feel free to include/reference in the TDB distribution (or ignore completely, of course ;) A few comments after having done so: nice, clean and simple. it was almost an ideal library to provide XS bindings for. the logg...

I (cross-)posted a few days ago about TDB files growing for individual printers. These TDB files are holding onto information about previous jobs after they have been printed. This is on AIX 5.3 that was just upgraded from 3.0.31 about 20 days ago. The problem now is we are bumping up against the "max print jobs" of 1000 for some really busy queues. Is there a way to remove this

...this is marked duplicate of is still showing as reopened) What works: The system has been joined onto the domain wbinfo -a DOM+username%password works consistently wbinfo -u and -g both work, though sometimes intermittently. It looks like it might be timing out? What else I see: net idmap dump tdb_file shows no UID/SID mappings. getent group/passwd show no AD users or groups I can't chown a file to a domain user (including the same one I can authenticate with wbinfo -a) Zeroth question: Am I just doing it wrong? I.e. do I need to manually add users and groups if I'm not going to enum...

...now what is really causing the problem, but the next output didn't look right: > wbinfo --dsgetdcname=Bliss ISHTAR \\ISHTAR 2 00000000-0000-0000-0000-000000000000 BLISS (null) 0x00000000 (null) (null) Is that supposed to be that way??? How do I fix/repair it? Tnx.... (just noticed the tdb_file lib on the perl CPAN archive is very outdated., and tdbtool is a very awkward way to make repairs, though I've used it successfully. Once. Are there any better tools for tdb editing? and better...ones that have samba specific labels??? ;-)....*sigh*...maybe there's an easier way.

...orked across operating systems. As a result, the .tdb files are filled with a few hundred drivers named after queues that don't exist, along with the normal dozen or so real drivers straight from the vendor. I cannot delete these from Windows and am working up a Perl script to do so using the TDB_File module. There is plenty of RAM and load on the server is very low (Pentium 3, 1.0 GHz). No problems with actual printing or driver downloads, and we are currently at 100 printers (eventually 200). Is it possible that tdb file plaque is to blame for our APW problems? If not, any suggestions as t...