this out?
- -Dan Sawyer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9nJ7TaB8ur/y6V8gRArm9AJ9rRc8yhDm5Catchqv4SXedOqs5qwCfSWS/
2IayciR10uTYysD/3F24UdE=
=TMQV
-END PGP SIGNATURE-
--
To unsubscribe from this list go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, I've removed the [printers] tab.
When I print locally, I do indeed use lpr -Pnec (or at least, that command
works very well). However, using that command from the client doesn't do a
thing for me (nor does printing from a gui program).
, Oct 03, 2002 at 09:32:49PM -0700, Dan Sawyer wrote:
-BEGIN PGP SIGNED MESSAGE-
thedude@floyd:~ cat kittykey.txt | smbclient //bob/nec -c 'print-'
added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0
Got a positive name query response from 192.168.1.101
misconfiguration in smb.conf, or
you need a different print filter.
Can you print text files from the server with the same command you have in
your smb.conf?
Joel
On Fri, Oct 04, 2002 at 10:05:14AM -0700, Dan Sawyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I now got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A followup to the last message:
I have configured the Samba server to act as a WINS server, so YAST2 finds it
now.
Upon examining the log.smbd file, I find that there are no log entries
generated when I try to print from the console or X on the
lprm command = /usr/bin/lprm -Pps %j
lppause command = /usr/sbin/lpc hold z53 %j
lpresume command = /usr/sbin/lpc release z53 %j
share modes = No
use client driver = yes
On Thu, Oct 03, 2002 at 12:47:27PM -0700, Dan Sawyer wrote:
-BEGIN PGP SIGNED MESSAGE
to bsd. Have you got a printing parameter in your
smb.conf?
Joel
On Sun, Oct 06, 2002 at 07:13:17PM -0700, Dan Sawyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Second update:
On the advice of someone else on this mailing list, I converted from BSD
printing to CUPS (still