similar to: printcap = coredump

I am unable to add drivers to network printer. I am logged in as a user who is allowed to write to those shares. But when ever I right click on the Properties of the printer when viewing \\DC\Printers and Faxes\PrinterName, Most of the tabs are disabled. I was able to install the drivers some time ago. But not any more. The more weird thing is that for some of the network printers, the Ports tab

In r271357 I've committed GDB pretty printer script for the following types - ArrayRef $1 = llvm::ArrayRef of length 3 = {1, 0, 7} - StringRef $2 = "foo\000bar" $3 = "fo" - SmallString $4 = "foo\000bar" - *SmallVector(Impl)* $5 = llvm::SmallVector of length 3, capacity 3 = {1, 0, 7} All of these visualizers are pretty simple, robust,

Hello, found no answer for the following elsewhere setting up samba on a Debian box: The printer is seen on the net from the clients but no printing is possible. $ smbclient -L pichuco Domain=[TANGO] OS=[Unix] Server=[Samba 3.0.10-Debian] Domain=[TANGO] OS=[Unix] Server=[Samba 3.0.10-Debian] Anonymous login successful Sharename Type Comment --------- ---- ------- public

Hi folks, I have a print server, running SPARC Solaris 9. I've just upgraded from Samba 3.0.10 to 3.0.22 and immediately hit system load issues which appear to be related to the use of "lpstat -v" to determine the available print queues. There are about 70 Unix print queues on this system. Running "lpstat -v" can take something like 20s of wall-clock time. lpstat

Previously, I was able to print within wine because the print dialogs would include the printers defined in the /etc/printcap file. Something changed, and now there are *no* printers defined within wine. I have tried reinstalling wine and all windows programs with no luck. Anyone have any hints where to start? Is there something else I need to configure? Richard rdlee@acm.org

Here's the scoop, Well Jeremy and I found the bug last night. Unfortunately it will not be fixed soon. The problem is a bug in our client side code wrt oversized PDUs. When the needed size > MAX_PDU_SIZE in a parsing struct, we need to fragment the PDU and use SMBwrite instead of a single SMBtrans. Fortunately, this has not gotten us into big trouble yet. Jeremy knows how to fix it,

Hi all, Am I the only person to have fallen over the following 'gotcha' ? Upgraded to 1.9.18p8 from 19.9.17p5 on Friday. Came in this morning to discover all Printing had died. Eventually tracked this down to the 'printcap name' setting in Samba jad changed. It default was '/etc/printcap' (it must have been as printing was fine up 17p5 and all previous versions).

According to all of the documentation I can find, an /etc/printcap file (or whatever filename is specified with the Printcap directive) is generated by cupsd ever time a printer is added or removed. On all of my CentOS 6.7 systems, this is NOT happening. I can restart cups and add or remove printers over and over and it still doesn't generate the printcap file. Is this a known issue, or is

Peter> My problem is browsing printers that names are more than Peter> 8 chars long. Any printer that is longer than 8 chars (in the Peter> printcap file) does not show up when browsing. Peter> Anybody else affected by this? Is there a fix? Jim> I had considered "fixing" the code but then I wondered whether I would run Jim> into DOS's 8.3 filenaming convention

Hi list. I'm having problems w/ printing using Samba on Redhat 8. Shared drives work fine yet my CUPS printing doesn't work. I sure appreciate any input. For what it's worth, I couldn't find any printing related errors in /var/log/samba/. I notice that the printcap doesn't have a sub-directory named cups like my old Debian box. Could that be it? Here's my smb.conf

I am using samba-2.2.7-3.7.2 on a redhat 7.2 server with an attached printer which is run by CUPS. It worked OK until I upgraded to samba-2.2.7-3.7.2. Now I can print locally on the server machine, but not from the windows machines on the LAN. The error message on the windows box is " Unable to create a print job." Another error, produced daily when samba is "re-initialized"

Hello all. I'm currently setting up a RedHat box with 4 nics to handle SMB printing for 4 separate subnets. I have CUPS printing set up and functioning. I have a separate smb.conf file configured to bind to one interface each, and everything is dandy. Here is where I hit my problem. When I have the following line from the conf file set as you see it, I see all the print queues without

Hi, following situation: 1) You create a raw printer (called "testprinter") under cups and leave the description-field (info-field) empty. cups will create an entry in /etc/printcap of the form testprinter|testprinter:rm=linux100:rp=testprinter: 2) You start samba with a standard [printers] and [print$] share. samba will expose the printqueue to the clients. 3) You upload a windows

Hi everybody, A few days ago I sent a message to this list with a related problem, now I have the problem "isolated". To reduce costs, we are using OLD Pentium's 133MHZ (166 and 233) as print servers, running CUPS. In some specific situations I have "legacy systems" running on DOS, so I need to "map" LPT1 on client, SAMBA is the solution. I'm using

Hi I?ve been carrying out some upgrades to our SCO Unixware 7 server. I?ve updated from 7.1.3 to 7.1.4, and then installed maintenance pack2. On the Samba side, this means that Samba has been upgraded from 2.2.8a (with UnxWare 7.1.3) to 3.0.0 (with UnixWare 7.1.4). Everything seemed to be working fine at this point. Samba was then upgraded to 3.0.10 (with maintenance pack 2), and I

I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris servers have no printers attached or accessible, just file service. Samba users authenticate off a Win2003 AD controller and get printing from that. I got rid of the "Unable to connect to CUPS Server" errors by adding to smb.conf the line printing=bsd but I am still getting smbd[4809]: [ID 702911 daemon.error]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Noticed the following when conducting torture tests today: [2006/05/12 14:04:24, 0] printing/pcap.c:pcap_cache_reload(159) Unable to open printcap file /etc/printcap for read! ...which to me, was interesting, because I was not under the impression I was using load printers. Apparently, at some point, it became the default. That's fine, but I

Hi, all I don?t know how can I configure the Samba print service in a HP-UX server. This OS don?t have the /etc/printcap file. What can I do in smb.conf ? Thank?s ------------------------------------------ Fernando Lanner Cardoso Cia. Zaffari Com. & Ind. Analista de Suporte/Inform?tica lanner@zaffari.com.br Porto Alegre - R.S. - Brasil ------------------------------------------

I am running Samba 2.0.6 successfully on a Linux machine. Currently I try to add the two printers in our net to Samba. Now I wonder which printer names in the printcap are shown when I do a 'smbclient -L <linux machine>'. The printcap contains something like remote22|HPL4kSC|HP Laserjet floor 4 ... remote21|HPLaser4|HP Laserjet floor 3 Now the first printer shows up as

I have played around with samba now for quite a while but couldnt print on my win2k box with koffice. with the command line smbclient it works: smbclient //server/hpdeskje -N -P -U user -c 'print hello' prints a text (from the file hello) "Hello World" Also a print to file file off my win2k box would print fine with smbclient. Only, I cant quite find out how the printcap