Sudev Barar wrote:
> On 8/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>> anyway...I found the solution
>> after moving binaries, directories and libraries (involved software:
>> cups, cups-lpd, a2ps, foomatic-rip, enscript, gs, mpage and perl) from
>> ltsp server to /opt/ltsp/i386..
Burke Almquist wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How about setting up and LPD-cups queue on the server for the printer?
Why do we need to run the LPD daemon on the client?
because users, during their activity, need to connect to the remote
tn3270 server which is configure
Burke Almquist wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe cups will listen for LPD traffic. So if you set it up that
way on the client side it should work.
Yes but I think that the only way to do it is setting up local
applications (cups & co.) to be run and I fear it's
I need to configure a locally connected printer not as a JetDirect
printer but as a LPR printer. So, that printer should be reachable by an
URI of this kind: lpd://IP_OF_THE_CLIENT/queue_name.
Is there a way to do that in LTSP or not? My users connect to a tn3270
server which needs to redirect i
