similar to: Printer Drivers Database Lost With 'rpm -Uvh'

Let's keep this on the samba list and not an interactive between you and me...Also, I prefer bottom posting so my reply will be at the bottom. On Fri, 2004-03-12 at 11:54, Lee Thao wrote: > Test page from cups using Postscript driver give printout saying printer is > not license for postsrcipt. Other drivers (Generic - PCL6) produces blank > sheet with a few chars in upper left,

Is this a samba issue or cups? I can print from a client just fine if I install a local printer attached to a local smb port (\\server\printershare). But when I create a "network" printer (using apw or double clicking on printershare in explorer), all I get for a test page (or from anything else actually) is a blank page with three non-alpha, greek lookin chars in the upper right.

Just deployed samba print server. Print jobs are going thru but getting: Mar 11 08:11:53 printsrv smbd[2017]: [2004/03/11 08:11:53, 0] smbd/connection.c: register_message_flags(220) Mar 11 08:11:53 printsrv smbd[2017]: register_message_flags: tdb_fetch failed Mail list archive thread said to use tdbbackup. What good will that do? What should I look for in tdbbackup -v? Should I delete

>Tait Shrum wrote: >| We have a Samba 3.01 pre3 server that acts as a print server among other >| things. When our users go to the add printer wizard in Windows, it >| doesn't show our samba server! The only way to add a printer is by >| manually entering the path. That's really inconvenient if you don't >| know the path. :) Is there some way we can resolve this?

For backup and redundancy purposes, I've been needing to replicate CUPS printer queues between two Samba servers, and came up with the following shell script. We use a fairly sizable number of CUPS printer queues printing in RAW mode, and install the printer drivers from the Windows clients, so all clients actually download the printer driver from Samba at first use. WARNING: This

Volker Lendecke wrote on Samba-digest: > Message: 10 > From: <Volker.Lendecke@SerNet.DE> > To: jerry@samba.org > Cc: tombork@web.de, Volker.Lendecke@SerNet.DE, samba@lists.samba.org > Subject: Re: [Samba] 2.2.6 and printer questions > Reply-To: Volker.Lendecke@SerNet.DE > Date: Mon, 04 Nov 2002 08:54:01 +0100 > Organization: Service Network GmbH, Goettingen,

Hi, Does someone know a document which explains the TDB structure. functionalites, and format of the TDB files etc. I need to understand why some of the TDBs like messages.tdb, unexpected.tdb, brlock if not read_only, locking.tdb, session.tdb, wins.tdb are called with TDB_CLEAR_IF_FIRST tdb flags. Why some TDBs are opend with O_RDWR|O_CREAT flags viz. gencache.tdb, group_mapping.tdb,

Samba 2.2.8a-1, RH8. ... So, I had to reinstall. Fortunately I had a back-up copy. I've installed everything and then went to back-up and brought back all the stuff from /etc/samba and /var/cache/samba and all /etc/cups and /etc/printcap*. Aparently samba is working corectly: All user/machine accounts are in place winbind OK... It's just that although I've restored the /home/printers

On Sat, Oct 17, 2015 at 04:13:30PM +0000, Howard, Stewart Jameson wrote: > gencache_notrans.tdb > gencache.tdb > mutex.tdb Just a side-remark: These tdbs have nothing to do with ctdb, they are purely local. > Because of the current steady size of this file compared > to its repeated, intermittent, and rapid inflation, we > suspect that there is some operational condition which

On Fri, Jul 01, 2016 at 10:00:21AM +0100, Alex Crow wrote: > We've had a strange issue after following the recommendations at > https://wiki.samba.org/index.php/Ping_pong, particularly the part > about mmap coherence. We are running CTDB/Samba over a MooseFS > clustered FS, and we'd not done the ping-pong before. After finding > that the mmap coherence test did not pass, we

Dear samba list after a classic upgrade i lose the printer drivers uploaded in NT Domain mode the drivers files are still present in print$ share but enumdrivers rpcclient command list no drivers... did i forgot a file in the dbdir during classicupgrade call or this data are not handled during classicupgrade ? Thanx

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > As a test, I changed the opening of the locking.tdb and brlock.tdb > files to use the TDB_INTERNAL flag, avoiding use of the fcntl(F_SETLK) > syscall for locking individual database records. Performance was a lot > snappier, with quite a bit less system time used. > > What is the scope of implementing shared

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

Thanks Michael, Please see the inline answers. > On Jan 10, 2016, at 5:16 PM, Michael Adam <obnox at samba.org> wrote: > > On 2016-01-10 at 17:58 +0000, Rowland penny wrote: >> On 10/01/16 17:05, Partha Sarathi wrote: >>> >>>> This could have a lot to do with the fact that idmap_rid & >>>> idmap_autorid calculate the uids differently

Hi There, I apologise for posting this again but our mail server went up in flames and I missed all of yesterdays posts due to bounced emails. The list then disabled my deliveries which I only realized hours afterward. Please resend me the post if there were any regarding this. Thanks and Regards Nic @> Matt McParland wrote: @> @> | I saw the same symptoms using Samba 3.0.1 and a

============================================================= "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

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Buffer overflow in cron daemon Advisory ID: RHSA-1999:030-01 Issue date: 1999-08-25 Updated on: Keywords: vixie-cron crond MAILTO Cross references: --------------------------------------------------------------------- 1. Topic: A buffer overflow exists in crond, the cron

On 2016-01-10 at 17:58 +0000, Rowland penny wrote: > On 10/01/16 17:05, Partha Sarathi wrote: > > > > > This could have a lot to do with the fact that idmap_rid & > > > idmap_autorid calculate the uids differently i.e if you have RID > > > '2025000', autorid would calculate this as '1102500000' , rid > > > would calculate this as

This will be the last stable release of CTDB 2.5.x. CTDB 2.5.6 should only be used with Samba releases prior to Samba 4.2.x (i.e. Samba releases 3.6.x, 4.0.x and 4.1.x). Please note that Samba releases 3.6.x, 4.0.x and 4.1.x are out of support. If you are still using any of these releases for clustered samba with CTDB 2.5.x, please switch to latest Samba 4.3.x or 4.4.0 (Since Samba 4.2.0 release