From: <[EMAIL PROTECTED]>
> I have a question on editing the
> printcap file. I created the original
> entries for printcap in RH7.2 with
> printconf but I needed to make changes
> to the default printer. They work great
> but it says you need to make the changes
> to princap.local. However this would be
> added to the end of the file. How would
> you change the entries and still have it
> be the default printer? Also wouldn't it
> than have a double entry?
>             Thank you
>             Linda Hanigan
>
>
I had the same problem when I upgraded to 7.2.  What we did was to initially
create the printers with printconf (so that had the right filters).  Then we
needed to have the default printer create banner pages, but printconf didn't
have an option for this, so we moved the printconf generated entry to
printcap.local.  One thing we found was that if a spool directory had the
world VOLATILE in it, printconf would delete that spool directory upon
rebooting the system, so we had to remove /var/spool/lpd/lp0/VOLATILE from
the spool directory.

We then noticed that the printouts were going to the wrong printer.  After
looking at the lpr (1) man pages, we added the following to /etc/profile:

PRINTER=lp0
export PRINTER

Scot


-----------------------------------------------------------------------------
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