Hi Van,

seems likt you discovered the expected behaviour:

[printsrv2] ~ $ lpc --h
--X option form illegal
usage: lpc [-a][-Ddebuglevel][-Pprinter][-Shost][-Uusername][-V] [command]
 with no command, reads from STDIN
  -a           - alias for -Pall
  -Ddebuglevel - debug level
  -Pprinter    - printer
  -Pprinter@host - printer on lpd server on host
  -Shost       - connect to lpd server on host
  -Uuser       - identify command as coming from user
  -V           - increase information verbosity
 commands:
 active    (printer[@host])        - check for active server
 abort     (printer[@host] | all)  - stop server
 class     printer[@host] (class | off)      - show/set class printing
 disable   (printer[@host] | all)  - disable queueing
 debug     (printer[@host] | all) debugparms - set debug level for printer
 down      (printer[@host] | all)  - disable printing and queueing
 enable    (printer[@host] | all)  - enable queueing
 flush     (printer[@host] | all)  - flush cached status
 hold      (printer[@host] | all) (name[@host] | job | all)*   - hold job
 holdall   (printer[@host] | all)  - hold all jobs on
 kill      (printer[@host] | all)  - stop and restart server
 lpd       (printer[@host])        - get LPD PID
 lpq       (printer[@host] | all) (name[@host] | job | all)*   - invoke
LPQ
 lprm      (printer[@host] | all) (name[@host]|host|job| all)* - invoke
LPRM
 msg       printer message text  - set status message
 move      printer (user|jobid)* target - move jobs to new queue
 noholdall (printer[@host] | all)  - hold all jobs off
 printcap  (printer[@host] | all)  - report printcap values
 quit                              - exit LPC
 redirect  (printer[@host] | all) (printer@host | off )*       - redirect
jobs
 redo      (printer[@host] | all) (name[@host] | job | all)*   - reprint
jobs
 release   (printer[@host] | all) (name[@host] | job | all)*   - release
jobs
 reread                            - LPD reread database information
 start     (printer[@host] | all)  - start printing
 status    (printer[@host] | all)  - status of printers
 stop      (printer[@host] | all)  - stop  printing
 topq      (printer[@host] | all) (name[@host] | job | all)*   - reorder
jobs
 up        (printer[@host] | all) - enable printing and queueing
   diagnostic:
      defaultq               - show default queue for LPD server
      defaults               - show default configuration values
      lang                   - show current i18n (iNTERNATIONALIZATIONn)
support
      client (printer | all) - client config and printcap information
      server (printer | all) - server config and printcap


best regards
        ~christoph


-- 
/*   Christoph Beyer     |   Office: Building 2b / 23     *\
 *   DESY                |    Phone: 040-8998-2317        *
 *   - IT -              |      Fax: 040-8998-4060        *
\*   22603 Hamburg       |     http://www.desy.de         */


On Wed, 31 Jul 2002, Van Sickler, Jim wrote:

> I discovered today the following commands don't work
> the same when typed in from the command line:
> (%p=hp4plus, in this case)
>
> These work:
> lpc -P%p stop
> lpc stop %p
>
> This doesn't:
> lpc stop -P%p
>
> I also discovered today that the default command
> syntax in the HOW-TO doesn't work from my Win2k
> wkstn:
>         queuepause command = /usr/sbin/lpc -P%p stop
>         queueresume command = /usr/sbin/lpc -P%p start
>
> this syntax won't work either:
>         queuepause command = /usr/sbin/lpc %p stop
>         queueresume command = /usr/sbin/lpc %p start
>
> The following syntax WILL pause/resume the printer:
>         queuepause command = /usr/local/sbin/lpc stop %p
>         queueresume command = /usr/local/sbin/lpc start %p
>
> So "lpc stop %p" / "lpc start %p" work in both situations...
>
> Would someone please change the syntax in the HOW-TO so
> that Section 2.12. reads:
>
>         queuepause command =  /usr/sbin/lpc stop %p
>         queueresume command = /usr/sbin/lpc start %p
>
> This will bring the commands in line with the correct
> (functional) syntax.  (After independent testing
> & confirmation, of course!)
>
> Thanks,
>   Jim
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> with:                           | example:
> subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems,  send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
>


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to