3b1: The lp daemon has left for the coast.

[Bob Ames]

In article <2572 at cadillac.CAD.MCC.COM> ned%cad at MCC.COM (Ned Nowotny) writes:
>
>[ lots of lp problems ]
>
>Ned Nowotny, MCC CAD Program, Box 200195, Austin, TX  78720  Ph: (512) 338-3715

I`ve had this problem with several of our UNIX PCs...

The Hotline once took about an hour, dialed-in, to fix this...
I have since done it several times...

It`s been a few months, so this may not be *EXACTLY* correct...
The usual disclaimers apply.  If you feel real familiar working in
root, then you probably won`t have any problems...

If you screw up your machine, don`t call me |-)

# zap lpsched
# cd /usr/spool/lp
# rm [A-Z]*
# cd class
# rm *
# cd ../interface
# rm *
# cd ../member
# rm *
# cd ../request
# rm -r *
# cd ..
# >default
# >log
# >oldlog
# rm outputq pstatus qstatus seqfile

now go to your Office and Setup your Printer...

Either right before of right after the previous step, you will need to
# /usr/lib/lpsched
{Since lpsched on UNIX PC is suid lp, either root or lp can execute it}

I can`t remember whether lpsched is done before or after the Setups...

BTW: I`ve also had to do this on a few Data General MV4000s running dgux.
On the DG, the lpadmin commands [that Printer-Setup runs on UNIX PC] had
to be exeuted prior to lpsched.

This seems to be a somewhat common problem among System V sites.

Bob Ames

Bob Ames   The National Organization for  the Reform of Marijuana Laws, NORML 
"Pot is the world's best source of complete protein, alcohol fuel, and paper,
is the best fire de-erosion seed, and is america's largest cash crop." - USDA
bob at rush.cts.com or ncr-sd!rush!bob at nosc.mil  or rutgers!ucsd!ncr-sd!rush!bob
619-741-UN2X "We each pay a fabulous price for our visions of paradise," Rush