Sponsored Content
Full Discussion: Cups print server
Top Forums UNIX for Advanced & Expert Users Cups print server Post 20628 by hassan2 on Tuesday 30th of April 2002 02:46:33 PM
Old 04-30-2002
Power Cups print server

I have just installed cup printing software on solaris 8 and i am able to print successfully
from the print server but unable to print from any of the print client in my local network subnet. i have enable browsing so that cups printer server could broadcaste itself to client. but still unable to print from client.

can you help please
 

9 More Discussions You Might Find Interesting

1. SCO

Print server configuration

Hi, Any one can help me to configure print server in SCO Unixware. I don't have any idea in this context. Any help would be highly appreciated. Best Regards, Tayyab (1 Reply)
Discussion started by: tayyabq8
1 Replies

2. Linux

holding print jobs in CUPS

Hi all. I have a problem with some printers that when I print a lot of jobs at once the printers gets stuck after 2 prints... (It's a barcode printers - DATAMAX). Whenever I'm printing each job separtly with a delay of a few seconds the printers work fine... So my question is how can I... (0 Replies)
Discussion started by: eliraza6
0 Replies

3. SCO

Printing as a CUPS client, only root can print!

Hi, i'm running Openserver 5.0.7 as a CUPS client for a Linux server. The root user can issue a "lpstat -t" to see the printers and can submit jobs without issues. The problem presents when I try to work as a regular user. If I issue an "lpstat -t" all I get after a few seconds is "lpstat:... (1 Reply)
Discussion started by: cyruspy
1 Replies

4. SCO

Printing to print server

hi everyone. i would like to know if it possible to send a file directly on printserver, ex: cat /etc/rc > /dev/lp0 (the parallel port) cat /etc/rc > /dev/laser1 (laser1 is a printer with a printserver) without using the lp command ? i m using sco openserver 5.0.7. thanks. (2 Replies)
Discussion started by: pwg274
2 Replies

5. Red Hat

CUPS print issue

Hi all, unable to print from linux box. Earlier it used to work fine. The print job is sitting in the queue and not going to printer. Removed queue job and tried again but no luck. Tried "cupsenable" but ended up with no success. I tried to print two text files as "root" with "lp " command... (0 Replies)
Discussion started by: lramsb4u
0 Replies

6. Red Hat

Restarting CUPS will restart existing print queues?

Hi, We need to restart CUPS service, and want to know if restarting CUPS service will stop/start existing printing queues? Thank you! (1 Reply)
Discussion started by: aixlover
1 Replies

7. Solaris

Setting up Solaris 10 to print to a windows print server

Guys, I have a issue that I am trying to rectify please advise. lpstat -t shows scheduler is running printer lext644 disabled since Mon Dec 02 19:48:18 2013. available.I have restarted the printer service and it shows online but the above says disabled. I have a lot of jobs in the print... (1 Reply)
Discussion started by: terrywhitejr
1 Replies

8. UNIX for Advanced & Expert Users

LPR CUPS to Windows server and queue.

Hi everyone, Our office has a lot of printers (label & laser), and sometimes it gets quite hard to configure a new printer in CUPS as most printer manufactures does not provide drivers/ppd for CUPS/LINUX/UNIX. So we are trying to move to a Windows Print Server and run a Proof of concept. We... (2 Replies)
Discussion started by: Syed Hussaini
2 Replies

9. UNIX for Beginners Questions & Answers

CUPS - Does a Submitted Print file live somehwere?

Hello All, When using CUPs. Does the file that gets printed live in some temp directory somewhere? For example, if a user submits a PDF file to be printed, does a cached copy of that PDF file live somewhere on the Server in a temporary directory, at least until its printed? # lpq -P... (1 Reply)
Discussion started by: mrm5102
1 Replies
cancel(1)																 cancel(1)

NAME
cancel - cancel print request SYNOPSIS
cancel [ request-ID...] [destination...] cancel -u user... [destination...] The cancel utility cancels print requests. There are two forms of the cancel command. The first form of cancel has two optional arguments: print requests (request-ID) and destinations (destination). Specifying request-ID with destination cancels request-ID on destination. Specifying only the destination cancels the current print request on destination. If desti- nation is not specified, cancel cancels the requested print request on all destinations. The second form of cancel cancels a user's print requests on specific destinations. Users can only cancel print requests associated with their username. By default, users can only cancel print requests on the host from which the print request was submitted. If a super-user has set user-equivalence=true in /etc/printers.conf on the print server, users can cancel print requests associated with their username on any host. Super-users can cancel print requests on the host from which the print request was submitted. Superusers can also cancel print requests from the print server. The print client commands locate destination information using the printers database in the name service switch. See nsswitch.conf(4), printers(4), and printers.conf(4) for details. The following options are supported: -u user The name of the user for which print requests are to be cancelled. Specify user as a username. The following operands are supported: destination The destination on which the print requests are to be canceled. destination is the name of a printer or class of printers (see lpadmin(1M)). If destination is not specified, cancel cancels the requested print request on all destinations. Specify destination using atomic or POSIX-style (server:destination), names. See for information regarding using POSIX-style des- tination names with cancel. See standards(5) for information regarding POSIX. request-ID The print request to be canceled. Specify request-ID using LP-style request IDs (destination-number). user The name of the user for which the print requests are to be cancelled. Specify user as a username. The following exit values are returned: 0 Successful completion. non-zero An error occurred. /var/spool/print/* LP print queue. $HOME/.printers User-configurable printer database. /etc/printers.conf System printer configuration database. printers.conf.byname NIS version of /etc/printers.conf. printers.org_dir NIS+ version of /etc/printers.conf. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpcu | +-----------------------------+-----------------------------+ lp(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpadmin( 1M), nsswitch.conf(4), printers(4), printers.conf(4), attributes(5), standards(5) POSIX-style destination names (server:destination) are treated as print requests if destination has the same format as an LP-style request- ID. See standards(5). Some print servers send cancelation notification to job owners when their print jobs have been cancelled. This notification usually comes in the form of an email message. Cancelation notices cannot be disabled on a Solaris server. 23 Feb 2005 cancel(1)
All times are GMT -4. The time now is 09:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy