Sponsored Content
Operating Systems Solaris bothered by bsd-gw[ID] lpr.error unknown printer (laser1) Post 98040 by kicko on Sunday 5th of February 2006 06:37:09 AM
Old 02-05-2006
bothered by bsd-gw[ID] lpr.error unknown printer (laser1)

Please help!

This message is creating a space problem in my /var/adm/messages and I don't know where it's coming from. I don't have any printer on my system.
 

9 More Discussions You Might Find Interesting

1. BSD

for linux and BSD users interested in Unix system V/bsd

for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide. ... (0 Replies)
Discussion started by: moxxx68
0 Replies

2. Programming

Error: unknown pseudo-op: `.weakref'

It's really strange that I have these error messages as follows when I tried to compile the C++ program. g++ -c -pipe -DOpenModeType=std::_Ios_Openmode -g -I. -o Obj/NP_genome_info.o NP_genome_info.cpp {standard input}: Assembler messages: {standard input}:10: Error: unknown pseudo-op:... (6 Replies)
Discussion started by: napapanbkk
6 Replies

3. Solaris

Unknown File Type error

Greetings there, i was trying to install an eclipse plugin on sunOS 4.x for the solaris sparc platform, and i got the following error: /usr/project/RAServer/bin> ./RAStart.sh Starting Agent Controller ld.so.1: RAServer: fatal: /usr/project/RAServer/lib/libxerces-c.so.24: unknown file type... (3 Replies)
Discussion started by: rohitsz
3 Replies

4. Solaris

"lpr.error] Warning: Received SIGPIPE" continuously appearing in logs

On a Solaris 8 print server we're continuously (every 2 minutes or so) getting these messages in the logs: printd: Warning: Received SIGPIPE; continuing I've applied this patch and restarted the printd daemon, but it doesn't help: #109320-22: SunOS 5.8: lp patch Does anyone have any idea what... (4 Replies)
Discussion started by: aussieos
4 Replies

5. Homework & Coursework Questions

FIFO possible blocking or unknown error

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Create a chat program using two FIFOs one for writing and the other for reading. The problem is something... (1 Reply)
Discussion started by: Ebodee
1 Replies

6. Shell Programming and Scripting

Unknown error - ``' unmatched

Hi Guys, I get the error while running below commands. Earlier the command used to execute, but after enclosing them in a function, the error is occuring backupPath=`echo $folderName | sed -e 's,/vobs/dte/itgClient/client/RegressionTestLibPostOHS/,,'` check_event=`cat... (7 Replies)
Discussion started by: ajincoep
7 Replies

7. Programming

Help Unknown Syntax Error

Please excuse me if this is an easy fix, for I am new to Unix and C '/problem1.c: line2: syntax error near unexpected token ` '/problem1.c: line2: `main() and for one program it has : command not found2: (above the syntax error) As mentioned this is in C not C++, I have complied all... (3 Replies)
Discussion started by: apolo93
3 Replies

8. UNIX for Advanced & Expert Users

Using SFTP Error Server Unknown

Not sure if this is the right forum and I apologies if not. I use Expression web to update our website on a UNIX server using SFTP. I use the same laptop, software, that works fine when at home, but when I travel, I tend to get a unknown server error. I am suspecting that it has something to do... (2 Replies)
Discussion started by: ae3799t
2 Replies

9. Shell Programming and Scripting

Getting unknown operator error while using a function

Hi, I wrote a function for the first time and not able to get the desired result. I have requirement to execute 10 queries. For this i wrote a function like below. function Command { typeset var SOL; if ; then CONNECTION="${CONNECTION} -e -time"; else SOL="`nzsql ${CONNECTION} -c... (8 Replies)
Discussion started by: Samah
8 Replies
lpc(1B)                                              SunOS/BSD Compatibility Package Commands                                              lpc(1B)

NAME
lpc - line printer control program SYNOPSIS
/usr/ucb/lpc [ command [ parameter...]] DESCRIPTION
The lpc utility controls the operation of local printers. Use lpc to perform the following functions: o start or stop a printer, o disable or enable a printer's spooling queue, o rearrange the order of jobs in a print queue, or o display the status of a printer print queue and printer daemon. lpc can be run from the command line or interactively. Specifying lpc with the optional command and parameter arguments causes lpc to interpret the first argument as an lpc command, and all other arguments as parameters to that command. Specifying lpc without arguments causes it to run interactively, prompting the user for lpc commands with lpc>. By redirecting the standard input, lpc can read commands from a file. USAGE
lpc commands may be typed in their entirety or abbreviated to an unambiguous substring. Some lpc commands are available to all users; oth- ers are available only to super-users. All users may execute the following lpc commands: ? [command ...] | help [command ...] Displays a short description of command. command is an lpc command. If command is not specified, displays a list of lpc commands. exit | quit Exits from lpc. status [all | printer ...] Displays the status of print daemons and print queues. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. Only a super-user may execute the following lpc commands: abort [all | printer ...] Terminates an active spooling daemon. Disables printing (by preventing new daemons from being started by lpr(1B)) for printer. all specifies this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. clean [all | printer ...] Removes files created in the print spool directory by the print daemon from printer 's print queue. all specifies that this command is performed on all locally attached printers.printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. disable [all | printer ...] Turns off the print queue for printer. Prevents new printer jobs from being entered into the print queue for printerby lpr(1B). all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. down [all | printer ...] [message] Turns the queue for printer off and disables printing on printer. Inserts message in the printer status file. message does not need to be quoted; multiple arguments to message are treated as arguments are to echo(1). Use down to take a printer down and inform users. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. enable [all | printer ...] Enables lpr(1B) to add new jobs in the spool queue. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. restart [all | printer ...] Attempts to start a new printer daemon. restart is useful when a print daemon dies unexpectedly and leaves jobs in the print queue. all specifies that this command is performed on all locally attached printers. printer indicates that this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. start [all | printer ...] Enables printing. Starts a spooling daemon for the printer. all specifies that this command is performed on all locally attached printers. printer indicates the command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. stop [all | printer ...] Stops a spooling daemon after the current job is complete. Disables printing at that time. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. topq printer [request-ID ...] [user ...] Moves request-ID or print jobs belonging to user on printer to the beginning of the print queue. Specify user as a user's login name. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. up [all | printer ...] Turns the queue for printer on and enables printing on printer. Deletes the message in the printer status file (inserted by down). Use up to undo the effects of down. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf( 4) for information regarding naming conventions for atomic names. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/var/spool/lp/* LP print queue. /var/spool/lp/system/pstatus Printer status information file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscplp | +-----------------------------+-----------------------------+ SEE ALSO
echo(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpsched(1M), lpshut(1M), svcadm(1M), printers.conf(4), attributes(5) DIAGNOSTICS
Use the svcs(1) utility to check if svc:/application/print/server is running. If it is not running, use svcadm enable svc:/applica- tion/print/server to start lpsched. See svcadm(1M). Ambiguous command Indicates that the lpc command or abbreviation matches more than one command. ?Invalid command Indicates that the lpc command or abbreviation is not recognized. ?Privileged command Indicates that the lpc command or abbreviation can be executed only by a super-user. lpc: printer: unknown printer to the print service Indicates that printer does not exist in the LP database. Check that printer was correctly specified. Use lpstat -p or the status command (see lpstat(1) or USAGE) to check the status of printers. lpc: error on opening queue to spooler Indicates that the connection to lpsched failed. Usually means that the printer server has died or is hung. Use /usr/lib/lp/lpsched to check if the printer spooler daemon is running. lpc: Can't send message to LP print service lpc: Can't receive message from LP print service Indicates that the LP print service stopped. Contact the LP administrator. lpc: Received unexpected message from LP print service Indicates a problem with the software. Contact the LP administrator. SunOS 5.10 5 Aug 2004 lpc(1B)
All times are GMT -4. The time now is 07:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy