Restart Stopped Printer

Alpha instructions for restarting stopped printer

#lpstat -t
no entries
autorad.stanref.com: Tue Dec 1 08:19:35 1998:
JetDirect lpd: no entries
autorad.stanref.com:
JetDirect lpd: no entries
autorad.stanref.com: Warning: lp7 is down:
autorad.stanref.com: Tue Dec 1 14:26:06 1998:
Rank Pri Owner Job Files Total Size
1st 0 yvette 657 (standard input) 22727 bytes
2nd 0 yvette 659 (standard input) 82014 bytes

# lpc up lp7
lp7:
queuing enabled
printing enabled
daemon started

#

lpc(8) lpc(8)

NAME

lpc - Line printer control program

SYNOPSIS

lpc [command [argument ...] ]

DESCRIPTION

The lpc command is used by the system administrator to control the operation of the line printer system. For each line printer configured in the /etc/printcap file, the lpc command may be used for disabling or enabling a printer; disabling or enabling the printer spooling queue; rearranging the order of jobs in a spooling queue or finding the status of printers, their associated spooling queues, and the printer daemons.

Without arguments, lpc prompts for commands from the standard input. When arguments are supplied, lpc interprets the first argument as a command and any remaining arguments as command parameters. The standard input may be redirected so that lpc reads commands from a file. The following is the list of recognized lpc commands:

• ? [command ...] - Prints a short description of each command specified in the argument list or, when no arguments are supplied, a list of the recognized commands.

• help [command ...] - Prints a short description of each command specified in the argument list or, when no arguments are supplied, a list of the recognized commands.

• abort [all | printer ...] - Terminates an active spooling daemon running on the local host, and then disables printing. This prevents new daemons from being started by lpr or lp for the specified printers.

• Clean [all | printer ...] - Removes any temporary files, data files, and control files that cannot be printed (files that do not form a complete printer job) from the specified printer queue(s) on the local machine.

• disable [all | printer ...] - Turns the specified printer queues off. This prevents new printer jobs from being entered into the queue by lpr or lp.

• down [all | printer ...] message ... - Turns the specified printer queue off, disables printing, and puts a message in the printer status file. The message does not need to be quoted because remaining arguments are treated the same as echo. The down command is normally used to take a printer down and let others know why. (The lpq command indicates that the printer is down and prints a status message.)

• enable [all | printer ...] - Enables spooling on the local queue for the listed printers. This allows lpr or lp to put new jobs in the spool queue.

• exit Exit from lpc.

• quit Exit from lpc.

• restart [all | printer ...] - Attempts to start a new printer daemon. This is useful when some abnormal condition causes the daemon to terminate unexpectedly and leave jobs in the queue. lpq reports that there is no daemon present when this condition occurs. When a daemon is stuck, you must first kill it and then restart.

• Start [all | printer ...] - Enables printing and starts a spooling daemon for the listed printers.

• status [printer ...] - Displays the status of daemons and queues on the local machine. When printer name parameters are not supplied, information about all printers is provided.

• stop [ all | printer ...] - Stops a spooling daemon after the current job has completed and disables printing.

• topq printer [jobnum ...] [user ...] - Places jobs in the order listed at the top of the printer queue.

• up [all | printer ...] - Enables all printing and starts a new printer daemon. Cancels the effect of the down command.

Normally, the clean subcommand allows you to remove all print jobs on the system or all jobs on a specified printer. However, clean does not remove the jobs in the spooling queues. Therefore, you should use the lprm command on a printer by printer basis to remove the jobs you want to eliminate.

ERRORS

The following diagnostic messages are possible.
?Ambiguous command
Abbreviation matches more than one command.
?Invalid command
No match was found.
Privileged command
Command may be executed by the superuser only.

FILES

/usr/sbin/lpc Specifies the command path.
/etc/printcap Specifies the printer description file.
/usr/spool/* Specifies print spool directories.
/usr/spool/*/lock Specifies the lock file for queue control.

RELATED INFORMATION

Commands: cancel(1),lp(1),lpd(8),lpr(1),lpq(1),lprm(1),lpstat(1).
Files: printcap(4).

Send Data To Compaq

Subject: procedure to send syscheck files

Date: Mon, 06 Jul 1998 16:41:50 -0400

From: Robert Walker <walker@alf.dec.com>

Organization: Digital Equipment Corporation

To: asouk@onlineaccess.net

Collecting crash files for Digital UNIX systems.
In order to analyze a crash, we'll need several files from
your system. The instructions that follow will explain how
you can collect these system files, package them, and send
them to our anonymous FTP site. You should be root on the
system which has crashed before starting these operations.
If you can't transfer them by FTP, you can tar them onto a
tape and mail them to the address included at the end of this
message. Be sure to indicate what type of tape drive was
used to write the tar archive. In the instructions below,
{Sequence Number} is used to denote the number assigned to
the call logged with Digital CSC - it looks like C980301-1234.
The best way to collect crash files is to retrieve the
latest sys_check script from
ftp://ftp.digital.com/pub/DEC/IAS/sys_check/sys_check.tar
Extract the tar file in a temporary directory and install
sys_check using:
# mv sys_check.tar /usr/tmp
# tar -xvf sys_check.tar
# cd OSFSYSCHECK*
# setld -l .

Install all subsets. When complete, as root run:
# sys_check -escalate
It will prompt for a temporary directory and the crash to
collect. When done there will be 1-4 files in the temp
directory specified. Use tar to collect these files into
one file named with the sequence number of the call with:

# cd /usr/tmp (or whichever directory you specified)
# tar -cvf {Sequence Number}.tar *escalate*

Then transfer this file to us using the instructions below
for submitting crash files.
To collect crash files manually do:

# cd /usr/adm/crash
Or the directory indicated by the SAVECORE_DIR variable in
the file /etc/rc.config.

# ls
These are any crash dump files. You'll see files similar to
vmunix.n, vmcore.n, and crash-data.n --> here ".n" is a number,
all crashes are saved with increasing values. crash-data.n may
or may not be present depending on the type of crash. If vmunix.n
is not present, copy /vmunix to this directory before beginning
the following instructions. Pick the largest "n" value you see
to analyze the most recent crash), then do:

# gzip vmcore."n" (or vmzcore."n" if 4.0D or above)
# gzip vmunix."n"
# gzip crash-data."n"
# cp /usr/adm/messages /usr/adm/crash/messages
# gzip messages
# cp /usr/adm/binary.errlog /usr/adm/crash/binary.errlog
# gzip binary.errlog
# cp /usr/sys/conf/HOSTNAME /usr/adm/crash/HOSTNAME

Here HOSTNAME is the hostname of the crashed machine - with it's
name in all CAPITAL letters.

# tar -cvf {Sequence Number}.tar crash-data.n.gz vmcore.n.gz \
vmunix.n.gz messages.gz binary.errlog.gz HOSTNAME
Submitting the collected crash files.
To FTP the crash file archive to Digital do:

# ftp xfer-alf.service.digital.com
(the IP address is 192.208.34.20 - if xfer-alf is down or full,
use xfer-cxo.service.digital.com at 192.208.35.20)

Name : anonymous
Password: <---enter your email address here
ftp> cd to_digital
ftp> binary
ftp> put {Sequence Number}.tar
ftp> quit
At this point, the files will now reside on our anonymous FTP site.
You can safely remove {Sequence Number}.tar to save disk space.
Please contact me at the Customer Support Center if you have any
problems with this process. When you've completed the FTP, please
inform me via email (if possible), so I'll know to begin my
inspection. Please include the file size and the site to which you
transferred the file. My email address is listed below.
walker@alf.dec.com
 

Divvy New Disk Drive
 

Divvy instructions – added scsi drive 8/8/98 Andy – 630 406 8969

1. Shutdown system and get the scsi device id’s.

1. Wall

^G^G^G^G^G
The system is coming down please log out.
^G^G^G^G^G
^D
2. Shutdown now
3. >>> prompt – ‘show device’

dka300.3.0.1.0 is the new cheetah scsi drive.
Dka600.6.0.1.0 CDRom
Scsi bus id is 7 – raid controller is probably 0.

4. B to boot and go to the X-windows interface.

1. Open the tool file cabinet in the right side of the lower task bar doo-dad.
2. Administrative Tools – Configuration – Disk Administration
3. Selected disk drive rrz3 to configure

Click so only a,b,g to configure. Make ‘a’ 997 Mb., and b and g equal – with a sliver left at the end of the drive to allow room for a bad block table and possible replacement blocks.

4. Terminal (use toolbar at bottom, left side, up arror, terminal – this gives you a root console.)
5. Swapon –a /dev/rz3a.

Backspace

To get the backspace to work ; stty erase "^h"
To reassign the interrupt key; stty intr "^C"

Filesystem Table

Aug 12 08:27 1998 /etc/fstab Page 1

root_domain#root / advfs rw 0 0
/proc /proc procfs rw 0 0
usr_domain#usr /usr advfs rw 0 0
var_domain#var /var advfs rw 0 0
/dev/re0b swap1 ufs sw 0 2
data1_domain#u /u advfs rw 0 0
data2_domain#v /v advfs rw 0 0
/v4/basic@servdell /u/basic/HIST2 nfs rw,bg 0 0
/dev/rx6c /mnt cdfs r 0 0
/dev/rz3a swap2 ufs sw 0 0
data3_domain#w1 /w1 advfs rw 0 0
data4_domain#w2 /w2 advfs rw 0 0
 

Alpha Model 2100 8-6-98

Find a free scsi address.
Determine Termination

Rails, Cabling, Cabinet, Power.
Low level format – none needed
A/b steps – in x windows administrator – Administrative tools.
Partitioning – swapon /dev/rz3h
Swap space assignment
Mounting
Raid array monitoring program
/sbin/rc3.d/S99/swxcr (swxcrmon)