hmmm,
this is really strange :-(
On Mon, 7 Jan 2002, Keith Rinaldo wrote:
> Hi, thanks for the reply.
>
> I've tried every possible way of implementing force_localhost that I know
> about... first we put it in the printcap file for each printer. Then we put
> it in lpd.conf. Then, I recomplied LPRng with --force_localhost-disabled.
> We're not having a problem with it looking at the local queues instead of
> remote queues, just the issue with it having to specify the FQDN. And the
> most interesting part is -- you only have to specify the FQDN if you're
> logged in and trying to print from the machine that acts as the print
> server. Any of our machines that access the print server remotely work
> fine, however if we're actually sitting on the server that runs LPRng, we
> have to specify the printer names as:
>
> lpr [EMAIL PROTECTED] testfile
>
> Otherwise, as I posted, it will not filter the file through ifhp properly
> and will not make any entries to the logs or accounting files.
>
> This is strange. Anyone?
>
> ---
> Keith Rinaldo
> Systems Administrator
> College of Engineering
> University of Nevada, Las Vegas
> Email: [EMAIL PROTECTED]
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, January 04, 2002 12:29 AM
> Subject: Re: LPRng: Very strange problem
>
>
> > hi,
> >
> > make sure 'force_localhost' is enabled in your lpd.conf file
> > ('force_localhost@' means it is disabled). For testpurpose you can also
> > just put force_localhost in the printcap...
> >
> > hope this helps
> >
> > regards
> > ~christoph
> >
> >
> >
> >
> >
> >
> > On Thu, 3 Jan 2002, Keith Rinaldo wrote:
> >
> > > This problem has been plaguing us for a few days now.
> > >
> > > After many many many recompiles and tinkering, we came to a rather
> > > interesting conclusion:
> > >
> > > If we run "lp" or "lpr" without a fully-qualified queue name, then for
> some
> > > reason the print job does not get filtered through ifhp, and none of the
> > > accounting information is updated in the /var/lpd/log/printername.acct
> file.
> > > However if we use a fully-qualified name, everything works!
> > >
> > > Example:
> > >
> > > lpr -Pmyprinter ./printcap
> > >
> > > .. will produce a stair-stepped printout of the printcap file, and
> nothing
> > > gets written to /var/lpd/log/myprinter.acct. However, calling lpr like
> > > this:
> > >
> > > lpr -Pmyprinter@localhost ./printcap
> > >
> > > ... works just fine! The output gets filtered through ifhp (and through
> > > a2ps respectively) and the accounting file is updated. This is very
> > > strange, and since we have a large number of users (around 6,000) it's
> very
> > > hard to tell them all that they suddenly need to use a fully-qualified
> name
> > > for the printers. We're using LPRng 3.8.4 and IFHP 3.5.2. An example
> > > excerpt from our printcap looks like this:
> > >
> > > myprinter|MyPrinter
> > > :[EMAIL PROTECTED]
> > > :lf=/var/lpd/log/myprinter.errs
> > > :sd=/var/spool/lpd/myprinter
> > > :ifhp=model=hp8100,pagecount,sync
> > > :filter=/usr/local/libexec/filters/ifhp
> > > :af=/var/lpd/log/myprinter.acct
> > >
> > > Is there something in lpd.conf or elsewhere that we can add to fix this
> > > strange behavior? And, while we're on the subject of strange behavior,
> > > programs such as lpc seem to be unhappy about something as well. I'm
> not
> > > sure if this is related to the other problem, but for some reason "lpc
> > > reread" just returns with no output and we don't know if it's sent the
> HUP
> > > to lpd or not... however, if we do "lpc reread all" then it reports that
> it
> > > sent the SIGHUP. This is just general wackiness and is very strange...
> and
> > > we've been beating our heads on the wall for 3 days... any help at all
> is
> > > GREATLY appreciated.
> > >
> > > Thanks.
> > >
> > >
> > > ---
> > > Keith Rinaldo
> > > Systems Administrator
> > > College of Engineering
> > > University of Nevada, Las Vegas
> > > Email: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> >
> > --------------------------------------------------------------------------
> ---
> > > 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.
> > --------------------------------------------------------------------------
> ---
> >
>
>
> -----------------------------------------------------------------------------
> 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.
-----------------------------------------------------------------------------
