Re: [suse-linux-s] Como auto depurar spool
Algunas veces se bloquean trabajos se imprimen pero el cups los reporta encolados, por algun motivo no se liberan del spool este problema como se podria solucionar. Ing. Alejandro Rojas Soporte Tecnico Interactivo Tel. 52 64 43 60 ---------- Original Message ---------------------------------- From: Camaleón <noelamac@gmail.com> Reply-To: Camaleón <noelamac@gmail.com> Date: Wed, 27 Jul 2005 19:14:19 +0200 El 27/07/05, Alejandro Rojas escribió:
Como se logra crear una depuracion he modificado el cupsd.conf donde creo hace referencia para esta accion. reinicie cups y sigue presentandoce la saturacion de este Filesys
En la página de CUPS podrás encontrar información más específica sobre el tema... el foro también te podría ser de gran ayuda: Article #264: How To Restrict Disk, Memory and CPU Usage http://www.cups.org/articles.php?L264+I0+T+P1+Qspool Saludos, -- Camaleón -- Para dar de baja la suscripción, mande un mensaje a: suse-linux-s-unsubscribe@suse.com Para obtener el resto de direcciones-comando, mande un mensaje a: suse-linux-s-help@suse.com ________________________________________________________________ Sent via the WebMail system at mail.stimx.com
El 27/07/05, Alejandro Rojas escribió:
Algunas veces se bloquean trabajos se imprimen pero el cups los reporta encolados, por algun motivo no se liberan del spool
Echa un vistazo a la documentación del administrador, seguro que hay alguna directiva que hace lo que buscas: Server directives http://www.cups.org/doc-1.1/sam.html#PRINTING_MANAGEMENT Saludos, -- Camaleón
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2005-07-27 a las 12:25 -0500, Alejandro Rojas escribió:
Algunas veces se bloquean trabajos se imprimen pero el cups los reporta encolados, por algun motivo no se liberan del spool
El cups hará eso mientras el "backend" no retorne un cero, es decir, sin error. A ver, de un correo del mantenedor del CUPS: |Date: Tue, 15 Feb 2005 17:15:10 +0100 (CET) |From: Johannes Meixner |Subject: Re: [SLE] CUPS question | | |Hello, | |On Feb 14 16:02 sargon wrote (shortened): |> Whenever I print a document, CUPS sends the document to a printer, |> then marks the printer stopped. The document does print, but I must |> delete the job (CUPS thinks it didn't print) and start the printer. | |It is the recipient of the backend which lets the backend think |the job was not successfully finished - see |http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html |"The Backends" | |I know this doesn't solve your problem but it explains |the reason. |As you didn't describe how your printer is connected, |I cannot give you more specific information what to do |in your particular case. | |In any case it schould help to make your own backend which |simply ignores the state of the recipient and exits always |successfully, but then you would of course lose jobs which |really didn't print successfully. | |Here a quick and dirty example for a selfmade backend for |the parallel port whith everything hardcoded in the backend |and a possible (but unlikely) race condition: |------------------------------------------------------------------ |#! /bin/bash |# see the "CUPS Software Programmers Manual": |# "Writing Filters" and "Writing Backends" | |# debug info in /var/log/cups/error_log |set -x | |# output "Device Discovery" information on stdout |if [ "$#" -eq "0" ] |then | echo 'direct lp0:/dev/lp0 "Unknown" "lp0 Printer"' | exit 0 |fi | |# have the input at fd0 (stdin) in any case |if [ -n "$6" ] |then | exec <"$6" |fi | |# infinite retries to access the device |until cat /dev/null >/dev/lp0 |do | echo 'INFO: cannot access /dev/lp0 - retry in 30 seconds' 1>&2 | sleep 30 |done |echo 'INFO: sending the data to /dev/lp0' 1>&2 | |# forward the data from stdin to the device |if cat - >/dev/lp0 |then | echo 'INFO:' 1>&2 | exit 0 |else | echo 'ERROR: failed to send the data to /dev/lp0' 1>&2 | exit 1 |fi |------------------------------------------------------------------ | - -- Saludos Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFC6tbbtTMYHG2NR9URApK3AJ43UtvLJzPZo3seWwbPrXQn3dF6jACbBMNY UsMVFbuVMbdrs34eQXeZ8Xg= =ap8D -----END PGP SIGNATURE-----
participants (3)
-
Alejandro Rojas
-
Camaleón
-
Carlos E. R.