similar to: Replicating printers, drivers, and settings between machines

Hi, We are a small company, which has just started using samba. Recently we have faced a few issues regarding the TDBs getting corrupted. I have read that the only way of getting around this issue, is to regularly take tdbbackups. But, this process needs a downtime of my samba server, which we would not want. Instead, is there a way where I can take the tdbbackup with out shutting down samba

Hello All, We have a problem with our samba-based print server (a redhat EL machine, running samba 3.2.8) occasionally getting corrupt ntprinters.tdb files. To combat it, I've been keeping nightly backups of the file, and restoring the latest whenever it crashes. This _almost_ works. When I restore the file, some of the printer settings - such as which driver it is using - seem to restore

============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF

============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF

Hi, testparm: --------- testparm shows: ERROR: the 'passwd program' (/usr/bin/passwd %u) requires a '%u' parameter. You can see, passwd program _is_ /usr/bin/passwd %u smbstatus: ---------- smbstatus command always shows processes _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for

===================================================================== "Well it takes a certain kind of girl to wear a backless dress with a Beretta 70 strapped to her thigh." James Bond, Skyfall ===================================================================== Release Announcements --------------------- This is is the latest stable release of Samba 4.0. Major

===================================================================== "Well it takes a certain kind of girl to wear a backless dress with a Beretta 70 strapped to her thigh." James Bond, Skyfall ===================================================================== Release Announcements --------------------- This is is the latest stable release of Samba 4.0. Major

Hi, we are using samba 3.0.24 as a printspooler for 80 network printers with a 500kB ntprinters.tdb for some years now. When we recently restarted samba we noticed that the ntprinters.tdb automatically shrinked to 24kB and printing was no longer possible. tdbdump of the original tdb-file is impossible too: "Failed to open ntprinters.tdb" The strange thing about this: we can solve

I've been looking throught the archives for a set of things to be done to migrate a install with samba 3.2.5 (lenny) to another server (wheezy) I can cope with the name change, that's no problem, but I'd like to avoid having to recreate the users on the new server, so far I tried this, without much success - scp the smb.conf to the new server - make hot backups cd /var/lib/samba

(yes, I know it's an old version of Samba but I *really* don't want to mess about upgrading right now) The server in question (SuSE Enterprise Linux 9) got itself in a tizz last night and was restarted cleanly via the shutdown -r command this morning. Everything comes back up, including Samba, and all is fine. Except that no-one can print. Nothing has changed in any of the

Hi @all, backing up and verifying _printing_ databases uses 20-96% cpu and takes a long time (there are only few entries and smbd and nmbd were not running): for i in /var/lock/samba/?*.tdb /var/lock/samba/printing/?*.tdb /etc/?*.tdb do date echo $i.samba.bak rm -f $i.samba.bak tdbbackup -s .samba.bak $i

Hi, Is there a way to populate customized settings of the drivers (printing related TDB files) from one Print Server to another? Here is the background: I am working on centralized driver distribution. Besides pushing all the drivers from a central location to the edges, the administrator should also be allowed to customize the drivers settings and the distribution should send those

I upgraded our 3.6.22 server to 4.1.11 this past week. We're using the non-AD NT4 setup and the upgrade went well except for two users mapping to different uids. I think at least one of these may have been caused by a very old smbpasswd file in /var/lib/samaba/private since the post-upgrade uid was the same as was in this ancient file. This led me to try and clean out old/unused files from

I have googled a lot, but I have found no examples of the correct use of the tdbbackup program. I am looking for some advice on how to use tdbbackup. I mean, I know I can simply run "tdbbackup *.tdb", but I was looking for in-depth information on when and how to use it, about best practices on using it, or what NOT to do. The Samba documentations says I should run it in my start/stop

Hi, Having a weird problem here. We've got Sambe 3.0.14a and cups 1.1.23 on a Debian system. I've run: cupsaddsmb -U RALPH\\jgoerzen -a -v Where RALPH is our PDC (and it also the machine I'm running this command on). The entire command *appears* to work, but: * None of the tdb files in /var/lib/samba, including ntforms.tdb, ntprinters.tdb, etc. have their date stamp updated.

I'm running: # smbd -V Version 3.0.24-2.28-1354-SUSE-CODE10 In a 600 print queues print server, but I'm experiencing a low performance while using the first queue. I was attaching ltrace/strace to some processes with "use mmap=no" and I found a BIG difference in information gathering in ntprinters.tdb between the first and the last print queue (using alphabetical sorting). This

Hello, in our organization we have a number of print servers scattered across several organizational units and departments. These servers are configured in a similar fashion (Samba 3+CUPS, raw print queues, point-and-print drivers for clients, authentication backend in a centralized directory). We had this idea of trying to set-up a machine in our central offices, for providing fail-over

hi! we seem to have a weird problem with our samba server and i hope somebody can point me in the right direction to find the cause of this problem setup: smbAT02:~# uname -a Linux smbAT02 2.6.18-5-amd64 #1 SMP Sat Dec 22 20:43:59 UTC 2007 x86_64 GNU/Linux .) the OS is debian stable (etch) .) samba version is 3.0.24-6etch9 .) the server has 8GB of RAM, 2 quad core intel cpus, about 1.5 TB of

Hi, we are experiencing periodic problems with our samba/cups setup: It seems like workstations which are locked but where users with the SePrintOperatorPrivilege are logged on destroy the ntprinters.tdb. This always takes place when the logrotate on the sambaserver runs the postrotatescript and restarts cups while the client is doing whatever it has to do. /var/log/messages says:

Hello List, offline fails also.. root at dc01:~# samba-tool domain backup offline --targetdir=/backup/linux/samba-dom-dc01-offline Creating targetdir /backup/linux/samba-dom-dc01-offline... running backup on dirs: /var/lib/samba/private /var/lib/samba /etc/samba Starting transaction on /var/lib/samba/private/secrets Starting transaction on /var/lib/samba/private/sam.ldb backing up