similar to: print jobs >4GB

My smb.conf file contains in the general section. max print jobs = 50 And i disabled the print queue using this command : disable PrintQueueName Therefore i would expect SAMBA to reject print jobs after the 50th. But in real life it does not, it continues to spool indefinitely. If i run a batch file from a client workstation to print continuously. It means the request to print is made

I have setup a dedicated print server running on RH 8 with Samba 2.2.5-10 and LPRng-3.8.9-6 to service a HP9000 printer. The print queue for this HP9000 gets it print jobs from a Windows server via a script and the queue is set to HOLDALL status. The HOLDALL status is necessary because the script runs overnight to produce the print jobs which can total anywhere from 500 to 12,000 individual print

Hi, I have Panasonic KX-P7105 printer connected through LPT1 port to the "D-link DP-101P+" print server. This printer is defined as raw and I am using it only for printing from different windows clients. Drivers are only on windows client side. On linux side I never print one page. Suddenly, in windows print spooler I can see already printed documents from every user. As

On occasion, we get a printer that becomes disabled, and jobs begin to queue up. When the issue is resolved, we re-enable the printer and usually all the jobs print out. However, sometimes the first job never prints, but the others do. The cups interface shows the job is stopped. IfI restart the job in the cups interface, it prints. Is there a way to determine, via the command line, if a

I'm running Samba 3.2.0-17.fc9 as a PDC, serving a printer using CUPS. When I look at the state of the printer under Windows XP I see that jobs which have completed are still listed. When I look in the printing/<printer>.tdb, there are all the jobs. There is nothing left in /var/spool/samba. There are only the completed control files in /var/spool/cups. It appears either that Samba

We have a print server running RHEL 4, w/ samba-3.0.33-0.15.el4 When viewed from windows, one queue on the system has the "remains" of 264 print jobs - some dating back to April, but I can't find where the information is coming from. Apparently the jobs print fine, but then the information sticks in the queue information. Running lpq on the Samba system shows: # lpq -a no

Hello! I?ve running samba 2.05a on suse linux 6.3 as a server with Win95 and Win98 clients and everything works fine. The only problem is, that users can?t manage (kill, resume,...) their print jobs once the print jobs are sent to the samba printer. When I read docs and books, it sounds that it?s possible to manage print jobs over network. As printing system I have "lpq command = plp",

Hi! on centos 4.4 (fresh install) I've got a problem with CUPS disabling a print queue between jobs. Sometimes it will print dozens of jobs before disabling the queue, sometimes it will do it after every job. This is a networked HP Laserjet printer at work. At home on a 4.4 box (upgraded from 4.3) with a local (parallel port) printer I've not seen this problem occur. (of course, I

Hi All, I installed cups and samba on redhat 9. Printer has been attached to the linux box . We can print from the linux box. We can print from windows clients too. But My problem is that when we print from windows, printer starts printing. But I want to hold print jobs instead. Then I want to go to cups web interface and release jobs. How can I do it? This is urgent. Pls let me know as soon

Hi every one, I am running cups and samba on Centos 4.3. printer prints immediately. I do not need it. But I need to hold print jobs until I manually relaese them . How can I do it ? pls let me know. i went to many sites and did many things. But The problem is still there? below gives some info I got it form the internet. I pls read it. I actully need it. pls help me. pls read the below CUPS

Hi, madly looking for an answer to this but haven't found it in the smb.conf man pages yet... I'm using samba for my print server. I use printing = cups with samba. Currently it looks like all print jobs are being retained in /var/spool/samba and it has just filled my var fs :-( and no one can print. I can't seem to find any parameters associated with pruning the jobs, or how long

Hi All, I am basically working on a product in which print-server is one of its functionalities. I am using SAMBA for sharing a printer which is connected to the hardware running Linux. I am running SAMBA and CUPS to manage the printing-options on the hardware. I am able to get prints when i give a print-command on the Windows PC which is connected via ethernet to the hardware. Also I am able to

Dear list, I have an Samba install 3.2.7-11.6-2057-SUSE-CODE11, and I would like my users to enable to cancel print jobs. Is the option printer admin suitable? And still available? Regards,

Printing from windows clients to Samba through cups works perfectly but old (finished) print jobs are piling up in the print queue for the printer on the client side. I never had this problem with the clients when the server was running RedHat 6.2 with Samba 2.2.8 and LPD. The server has been replaced with a server running a RedHat Enterprise Linux rebuild (TaoLinux). The Samba version is

Hello all. I've been running Samba for quite some time but am now trying to move it up from (some rather limited) file sharing into being a full PDC for our network. I figured out all the "hard stuff" but am having a heck of a time with the printing. What I need to make sure of is that certain people can pause/delete, etc print jobs for other users, as well as start or stop the

Hello all, I am running Samba 3.0.9 with CUPS 1.1.17. When my windows user try to pause print jobs it does not work and gives them an error "Error Processing Command" in Windows. If they try to cancel a print job it doesn't give any error. It just disappears from the print queue and print anyway. Could someone point me in the right direction? Thanks all Dominic Iadicicco

Hi Everyone, Having problem wuth truncated print jobs, I'm looking for help: - New server with Samba 4.4.3 compiled from source, Linux Centos 7.2 x86_64; - with patched source3/smbd/reply.c to avoid truncated smbd replies to old clients, as provided by Jeremy here: http://samba-technical.samba.narkive.com/g3YL4vmY/dos-clients-slow-on-samba-4-1-7-bug-10422 (works perfect, thanks!) - Several

When sending print jobs back to back .. say 5 times or so .. sometimes a character or two get droped .. causing the printout to be some what garbled. This happens from NT as well ... heh .. which is really fun when they're printing postscript .. cause when the 1st character or so is droped from a postscript print job .. it's postscript commands are printed out as ascii. Is anyone else out

We have a server running Centos-3 with all latest updates. The server hosts 3 printers for us which are accessed by various Windows clients. About 3 months ago we noticed that, after a cups update, if you looked at the print queues in Windows they would show old jobs that had long been printed. After a further cups update this quirk went away but it's just come backs again - possibly after

Hello! i've been using samba 2.2.5 with an windows XP, and noticed that print jobs submitted to the (samba) print server don't appear in the printer properties page; is this normal? It seems to be the case on all win32 clients. --------------------------------- Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes -------------- next part -------------- HTML