On Tue, 2006-07-04 at 21:58 +0930, Tim wrote: > Aaron Konstam: > >>> No entry is needed in the clent.conf file if the machines are on the > >>> same lan. In fact if you put that line in a clients client.conf file > >>> the machine will not be able to print to a local printer on the client > >>> machine. > > Tim: > >> Not entirely true... Just to be pedantic, if you put the machines own > >> name in the client.conf file, it will print to itself. The client's own > >> other CUPS config files can be used to refer to other printers. > >> > >> Messy, but do-able. ;-) Though I can't think why you might want to do > >> that. > > Aaron Konstam: > > I don't think what you said is pedantic, just wrong. > > I don't know that it is. "Wrong", in computing terms, generally meaning > something that you can't or mustn't to. This just seems odd... > > The reason I tried that, was because I had two servers on a network, one > of the servers also gets used as a computer, and I wanted to try > printing to the other server (instead of itself) to test out something. > So, rather than screw around with an system that was working well, I > merely adjusted the client.conf file so it used the other server, rather > than itself. Then, afterwards, wrote its own name into the client.conf > for the sake of seeing what happened (whether it'd go back to printing > to itself, which it did). Let us be clear. What I am saying is that if in the client.conf file you identify the server as another machine it will not also print to its own printer. Are you claiming that is incorrect? However, if the client and server are on the same lan and you put no server name in the client.conf file as a server the client will be able to print to both the servers printers and its own printer. I went through this about a year ago and that is wnat happened in my sysem. If the two machines are not on the same lan then additional configuration must be done in the cupsd.conf of the server but to print to its own printer the client must not have any server declared in its own client.conf file. > > Reading into the docs, it suggests that if you haven't configured the > client.conf file, the default is to use localhost. Now, whether you > refer to a particular machine as localhost, or its unique hostname, > you're still referring to itself. You get the same result - it prints > to its own server. Which appears to be how a particular machine prints > to its own directly connected printer, through CUPS (client to server, > within the box). > > Do a quick search for ServerName in the Administrator's Manual. > > > If you identify the client machine as its own server its printer is > > the only one it will be able to print to. I am not sure what CUPS > > config files you suggest will allow printing to other printers on the > > network. Which are they? > > Look through the docs/example comments in the cupsd.conf file, and you > can see how to configure a server to also use non-locally connected > printers (i.e. ones not on its own parallel, USB, or other types of > ports), ones on a network. You can make one server a kind of hub for > printers across your network. > > See: BrowsePoll & BrowseRelay in the Administrator's Manual. > > -- > (Currently running FC4, occasionally trying FC5.) > > Don't send private replies to my address, the mailbox is ignored. > I read messages from the public lists. > -- ======================================================================= Thus spake the master programmer: "You can demonstrate a program for a corporate executive, but you can't make him computer literate." -- Geoffrey James, "The Tao of Programming" ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
