-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Bock wrote:
>service printer
>{
>socket_type = stream
>protocol = tcp
>wait = no
>user = lp
>server = /usr/lib/cups/daemon/cups-lpd
>server_args = -o raw
>disable = no
>}
>
>The option -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Bock wrote:
>Just for completeness, in case somebody is searching the list archives.
>The printer service that I am using right now looks like this:
>
>The option -o raw was necessary to force cups to figure out itself what
>kind of file ty
Just for completeness, in case somebody is searching the list archives.
The printer service that I am using right now looks like this:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
server = /usr/lib/cups/daemon/cups-lpd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Bock wrote:
>thanks a lot, that did it. I added the printer service and now things are
>working the way they should. I wonder why this isn't mentioned anywhere
>int the cups documentation, but maybe I just didn't find it there.
I got most
On Tue, 4 Jun 2002, David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nicolas Bock wrote:
>
> >Shouldn't there be a printer port on my server?
>
> service printer
> {
> socket_type = stream
> protocol = tcp
> wait = no
> user = lp
> ser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Bock wrote:
>Shouldn't there be a printer port on my server?
Caveat: I have not yet had any luck getting Red Hat's supplied CUPS
package to work. I built my own on 7.2, and continue to use that build
on 7.3. YMM therefore V.
lpd and CUP
Hi everybody,
I am having some difficulties with the configuration of CUPS. As I
understand, from reading the administrator's manual, cups should be open
to remote requests, but so far I have to conclude that it isn't.
So far I did the following: installed a local printer, local printing
works g
