Prev: how to get access to patches at sunsolve.sun.com
Next: intel bootserver for sparc
From: Chris Eckert on 12 May 2010 16:26
"Hugo" <hugo(a)idontwantspam.com> wrote:
>
> lpadmin -p hptest -o nobanner, protocol=tcp, dest=192.168.1.230:9100
> -m
> netstandard -v /dev/null
> enable hptest
> accept hptest

on my system (solaris 10 u8) the -v option
needs to appear before -o, also i cannot
concatenate options using commas.

my command thus looks like:
lpadmin -p hplj1320nw -v /dev/null -o nobanner -o protocol=tcp -o
dest=192.168.11.230:9100 -m netstandard

> try your text file again and see if anything happens, if that works,
> try
> your gedit.

the printer is successfully created but nothing happens when i issue 'lp
/etc/group'.
for a short period of time the job appears
in lpq listings but never in lpstat listings.
then disappears...

chris

--
Chris Eckert (mobile)
From: Chris Eckert on 12 May 2010 16:43
John D Groenveld <groenvel(a)cse.psu.edu> wrote:

> # touch /tmp/foobar.out
> # chown lp /tmp/foobar.out
> # chmod 600 /tmp/foobar.out
> # lpadmin -p foobar -v /tmp/foobar.out -m standard_foomatic \
> -n
> /usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_1320-Postscript.ppd.gz
> \
> -o dest=HPHP1320NW_IP_ADDRESS:9100 -o Duplex=DuplexNoTumble \
> -o banner=never -T PS -I postscript
> # /bin/enable foobar
> # /usr/sbin/accept foobar
> # lp -d foobar /etc/release


ok, did that. and so the printer was created.


> Does /tmp/foobar.out contain a 500+ lines of PostScript
> including these four:
> ()0(Solaris 10 10/09 s10x_u8wos_08a X86)23 L
> ()0(Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.)11 L
> ()0(Use is subject to license terms.)24 L
> ()0(Assembled 16 September 2009)27 L


yes, the four lines appear at the end of the
postscript file.

but sadly nothing gets printed.

what's wrong here? the very same
printer works in my local network from
linux, macos and windows machines.

chris

--
Chris Eckert (mobile)
From: Hugo on 12 May 2010 17:41

On 12-May-2010, Chris Eckert <eckert(a)alphanet.ch> wrote:

> what's wrong here? the very same
> printer works in my local network from
> linux, macos and windows machines.

Im joining this thread so we dont have two running simaltaneously under the
same name.

Linux and MacOS are almost certainly running CUPS (Common Unix Printing
System), which you can get for Solaris, and HP will do driver's for ..

I didnt think it did, but the HP 1320 must be using some part of HP's
Jet/NetAdmin system, otherwise what you've tried so far should just work -
and Ive never really got that working from Solaris' print system even though
it should be possible.

I'll be watching this thread with interest to see if John can get anything
working with you ... Otherwise, I can only suggest moving to CUPS.

Regards
From: John D Groenveld on 12 May 2010 18:06
In article <650174647295389320.833413eckert-alphanet.ch(a)news1.open-news-network.org>,
Chris Eckert <eckert(a)alphanet.ch> wrote:
>yes, the four lines appear at the end of the
>postscript file.

Excellent!

>but sadly nothing gets printed.

Nothing should print as this was just a test to see
if you could print to a plain file as the output device.

Now switch it back:
# lpadmin -p foobar -v /dev/null -m netstandard_foomatic \
-n /usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_1320-Postscript.ppd.gz \
-o dest=HPHP1320NW_IP_ADDRESS:9100 -o Duplex=DuplexNoTumble \
-o banner=never -T PS -I postscript
# lp -d foobar /etc/release

John
groenveld(a)acm.org
From: Chris Eckert on 13 May 2010 17:46
John D Groenveld <groenvel(a)cse.psu.edu> wrote:
> In article
> <650174647295389320.833413eckert-alphanet.ch(a)news1.open-news-network.org>,
> Chris Eckert <eckert(a)alphanet.ch> wrote:
> >yes, the four lines appear at the end of the
> >postscript file.
>
> Excellent!
>
> >but sadly nothing gets printed.
>
> Nothing should print as this was just a test to see
> if you could print to a plain file as the output device.
>
> Now switch it back:
> # lpadmin -p foobar -v /dev/null -m netstandard_foomatic \
> -n
> /usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_1320-Postscript.ppd.gz
> \
> -o dest=HPHP1320NW_IP_ADDRESS:9100 -o Duplex=DuplexNoTumble \
> -o banner=never -T PS -I postscript
> # lp -d foobar /etc/release
>
> John
> groenveld(a)acm.org
>

ok. as it looks now, the whole problem
was a missing acl entry on my hp laserjet
1320nw. shame on me!

i can now create the printer using the
jds gui as well as the lpadmin cli command.

under u8 it appears as "postscript, common"
in gui print dialogues instead of its name
defined during installation. that's misleading.

chris

--
Chris Eckert (mobile)
First  |  Prev  | 
Pages: 1 2
Prev: how to get access to patches at sunsolve.sun.com
Next: intel bootserver for sparc