Sponsored Content
Top Forums Shell Programming and Scripting Avoid interaction into script Post 302462889 by lyapma on Friday 15th of October 2010 08:56:49 AM
Old 10-15-2010
It's OK.

I use lpc statut PrinterName and i finally write a script.
Thanks you
 

10 More Discussions You Might Find Interesting

1. HP-UX

Boot interaction

Hi All, I am the new boy on the Block with HP-UX. To get to the point, I have a Hp-ux (C200) workstation running on Hp-ux 11.x Operating System. A week ago when practicing on file access permission, I have set the permission on a directory (perhaps a file I am not sure) to 0544 and did... (19 Replies)
Discussion started by: mhossien
19 Replies

2. Shell Programming and Scripting

avoid displaying errors while executing a script

Hi all, I am running a script on bash shell, although it gives me the desired output, it displays some errors at the prompt like this directory doesnt exists unary operator etc etc Is there someway to avoid these errors ?? Its very annoying to have these errors while the script is... (4 Replies)
Discussion started by: vikas027
4 Replies

3. Programming

Needed help in a ruby script with user interaction involved!

Hi all, I am struck at this point and needed some help in ruby I wanted to write a script that accepts the no of VNICs the user wants to create and then ask for the name of each Vnic he wants then use these names to create the corresponding Vnics Eg: suppose that there are 2 Vnics to be... (0 Replies)
Discussion started by: wrapster
0 Replies

4. Shell Programming and Scripting

Error with script interaction

Hi I have a script which is coming up with errors when I iterate over a list of database names. When I print out the values it shows a title & underline...if I then attach "hi" to the print out I get : hi TBS_SVC_NAME hi ------------------------------ hi bkahepa hi hi echo "select... (14 Replies)
Discussion started by: Dird
14 Replies

5. Shell Programming and Scripting

Avoid file creation in a script...achive same result

Guys following lines help me in getting numbers from PID column ,to be thrown into first column of a CSV file. COLUMNS=2047 /usr/bin/ps -eo pid,ppid,uid,user,args | grep -v "PID" > /tmp/masterPID.txt cat /tmp/masterPID.txt|while read line do PID=`echo $line|awk '{print $1}'` echo "$PID"... (4 Replies)
Discussion started by: ak835
4 Replies

6. Shell Programming and Scripting

using SSH with my script and avoid logging in manually

Hi Guys. I have 3 variables $HOST $Username $Password I want to connect to a remote server using SFTP. usr/bin/sftp -o Cipher=blowfish $HostWhere do I put in the options for the username and pwd??? I have tried different ways and nothing works. It keeps coming back and promting me. ... (5 Replies)
Discussion started by: ramangill
5 Replies

7. Shell Programming and Scripting

Avoid script running multiple times by filelock

Sometimes we need a single instance of a script to run at a time. Meaning, the script itself should detects whether any instances of himself are still running and act accordingly. When multiple instances of one script running, it’s easy to cause problems. I’ve ever seen that about 350 instances... (4 Replies)
Discussion started by: edenCC
4 Replies

8. Shell Programming and Scripting

how do i avoid system hang due to ssh in script?

I have a script that collects data from about 200 servers using 'ssh'. The problem is that, process sometime hangs at some point stopping the execution of the script. Please give me some idea how can I force the execution to jump to the next step if there arises any problem !! Thanks for replies if... (1 Reply)
Discussion started by: mdangol
1 Replies

9. Shell Programming and Scripting

How to avoid locks while loading database through UNIX script.?

Hi, I have the following requirement: I have load_cdr as main scriptwhich loads all the file records into vertica database through unix script. But there are two files which try to update same table..n thats y my script is getting failed... Can any1 give me some logic how to over come this... (6 Replies)
Discussion started by: gnnsprapa
6 Replies

10. UNIX for Beginners Questions & Answers

How to avoid banner o/p in script.?

hi I am writing a script where I don't want to display banner on terminal. below is the script. what should I do to avoid this without doing any permanent changes. I just don't want to avoid printing banner in my script. for i in `cat IP` do ssh root@$i '... (4 Replies)
Discussion started by: scriptor
4 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 01:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy