> Excuse me suggesting the obvious, but you may want to check > - contents of /etc/resolv.conf > - "domain_name" entry in /etc/lpd.conf (or wherever you put your > lpd.conf file) >
Been there, done that, got the T-shirt. :) It's a very strange problem, and I don't think it has anything to do with it not knowing what the domain is... it's quite perplexing. As I put in my original post, here's an example of what happens: lpr -Pmyprinter testpage will actually print. It will send the job to myprinter.egr.unlv.edu as it is supposed to, suggesting that the domain name is recognized properly. However, print job does not seem to filter through ifhp, because, assuming that "testpage" is a plain ASCII file, we get stair-stepped output of the text on the remote printer. None of the logs or accounting files get updated for that print job, either. However, the following WORKS: lpr [EMAIL PROTECTED] testpage OR lpr Pmyprinter@localhost testpage These commands will send the output through ifhp (and appropriately through a2ps for the ASCII files) and will update the log files and accounting files. We never used to have to specify the @machinename part before, and this is very very odd. It's also very very inconvenient for our 6,000-some-odd users that log in remotely to this server to have to be trained to format the print requests differently. We also still have the problem (and this is NOT a trivial one to ignore) of LPC bombing out on us. for instance: lpc reread simply returns back to the command line with no output, and I'm pretty sure it's not sending the SIGHUP to lpd Thanks for the help, if you come up with anything else please let me know... I'll try ANYTHING!!! :) --- Keith Rinaldo Systems Administrator College of Engineering University of Nevada, Las Vegas Email: [EMAIL PROTECTED] ----- Original Message ----- From: "John Perkins" <[EMAIL PROTECTED]> To: "Keith Rinaldo" <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 2:06 PM Subject: Re: LPRng: Very strange problem > > 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: > > Excuse me suggesting the obvious, but you may want to check > - contents of /etc/resolv.conf > - "domain_name" entry in /etc/lpd.conf (or wherever you put your > lpd.conf file) > > Make sure the domain is set correctly in both places; you may have to stop and > restart the lpd process to read in any changes in lpd.conf (not sure if lpc > reread will do the trick or not). > > -- > ============================================================================ > John Perkins | University of Wisconsin-Madison > Associate Researcher | Department of Computer Science > [EMAIL PROTECTED] | 1210 W. Dayton St. > 608-262-0438/608-262-9997 FAX | Madison, WI 53706-1685 > ============================================================================ > > > > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
