Hi



I installed cups on solaris 8 successfully and able to give print on my
line printer.



  The problem is /opt/sfw/cups/var/log/cups/page_log is not giving me
  the right count of number of pages given by the user.



 $> cat page_log



printer root 1 [16/Sep/2003:09:15:19 +0500] 1 1

printer test 2 [16/Sep/2003:09:29:48 +0500] 1 1

printer root 3 [17/Sep/2003:03:52:15 +0500] 1 1

printer root 4 [17/Sep/2003:03:55:41 +0500] 1 1

printer root 5 [17/Sep/2003:05:25:55 +0500] 1 1

printer test 6 [17/Sep/2003:05:27:55 +0500] 1 1

printer test 7 [17/Sep/2003:05:28:46 +0500] 1 1

printer test 8 [17/Sep/2003:05:34:16 +0500] 1 1

printer test 9 [17/Sep/2003:05:37:40 +0500] 1 1

print root 11 [19/Sep/2003:07:57:56 +0500] 1 1







  But in every print request I have given pages with more than one page
  in length.



  How to enable page accounting on solaris using cups.





   some more  details :



   $> /opt/sfw/cups/bin/lpstat -v

   device for print: socket://202.141.151.1:9100/





   $> uname -a

   SunOS SunSol 5.8 Generic_108528-22 sun4u sparc



regards

CVR


--
Posted via http://dbforums.com

"cvreddy5" <member40387@dbforums.com> wrote in message
news:3390608.1063982172@dbforums.com...
>
> Hi
>
>
>
> I installed cups on solaris 8 successfully and able to give print on my
> line printer.

Maybe that is what caused your posting to be so messed up too?  All the
extra line spacing?

Why would you want to use Cups in the first place?

"Kevin" <news@tnet.com> writes:
>
>"cvreddy5" <member40387@dbforums.com> wrote in message
>news:3390608.1063982172@dbforums.com...
>>
>> Hi
>>
>>
>>
>> I installed cups on solaris 8 successfully and able to give print on my
>> line printer.
>
>Maybe that is what caused your posting to be so messed up too?  All the
>extra line spacing?
>
>Why would you want to use Cups in the first place?

Because the SysV print spooler sucks donkey d*ck?


-- 
       "The road to Paradise is through Intercourse."
The uk.transport FAQ; http://www.huge.org.uk/transport/FAQ.html
        [email me at huge [at] huge [dot] org [dot] uk]

"Huge" <huge@ukmisc.org.uk> wrote in message
news:bkfkk0$bph$2@anubis.demon.co.uk...
> "Kevin" <news@tnet.com> writes:
> >
> >Why would you want to use Cups in the first place?
>
> Because the SysV print spooler sucks donkey d*ck?

Luckily we don't have any donkey's here so that would not be a problem.

We don't allow animals in the data center anyway.

In article <l5acnf9MkszK9faiXTWJhg@giganews.com>,
 "Kevin" <news@tnet.com> wrote:

> "Huge" <huge@ukmisc.org.uk> wrote in message
> news:bkfkk0$bph$2@anubis.demon.co.uk...
> > "Kevin" <news@tnet.com> writes:
> > >
> > >Why would you want to use Cups in the first place?
> >
> > Because the SysV print spooler sucks donkey d*ck?
> 
> Luckily we don't have any donkey's here so that would not be a problem.
> 
> We don't allow animals in the data center anyway.

What about _management_?  They're allowed in, aren't they?

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...

In article <bkfkk0$bph$2@anubis.demon.co.uk>,
	huge@ukmisc.org.uk (Huge) writes:
> "Kevin" <news@tnet.com> writes:
>>
>>"cvreddy5" <member40387@dbforums.com> wrote in message
>>news:3390608.1063982172@dbforums.com...
>>>
>>> Hi
>>>
>>>
>>>
>>> I installed cups on solaris 8 successfully and able to give print on my
>>> line printer.
>>
>>Maybe that is what caused your posting to be so messed up too?  All the
>>extra line spacing?
>>
>>Why would you want to use Cups in the first place?
> 
> Because the SysV print spooler sucks donkey d*ck?

How so?  I've gotten it to do everything I've ever wanted, albeit with
some work.  I had something like netstandard way before Sun did (and used
an existing freeware spool-less lpr clone client in place of netpr). Right
now, I have a Lexmark that can handle either PCL5 or PostScript; all
non-raw (type of either raw or same as the printer type, which is
something made-up, _not_ PS) jobs go through my own filter which wraps
them with commands to force the right type (PCL5 or PostScript), set the
#copies (cuz the stupid Lexmark ignores the lpr/lpd control data), and do
some little stuff like set the jobname on the printer's display. It took
one C program plus some fooling with the filter scripts and a custom
interface script, a couple nights work.  I also have an Epson C80,
driven with a custom interface script that calls another script that
frontends gs by converting friendly -o options into gs and gs driver-level
options to allow user-specifiable resolution, etc.

Every damn thing works - i.e. man -t manpage   actually prints to
whichever is the default printer, PostScript and text jobs (and some
filters you prolly never heard of) all do their thing, etc.

You can make it bark at the moon or lay eggs or walk and talk if you like.
If you have some faxing software, it doesn't take that much work to set it
up to let you "print" to a remote fax, either.

The only thing I haven't gotten it to do (but I haven't tried, either)
is printer accounting.  But it looks like there are hooks for that,
and that the supplied output filters support it.  I rather suspect I
could make that work if I wanted to.

The only thing it can't do is allow proper control of autorecognition;
"starts with %! = PostScript, else text" is hardcoded if the user doesn't
specify a content-type.  You can kluge around that by making sure no
printer accepts text directly, and that the only text-to-anything filters
you have are those you create which handle recognition and conversion
themselves.  But then someone can't force content type "simple" (plain
text), as in if they wanted to print a listing of a PostScript program; or
rather, your own autorecognition can't tell whether lp's autorecognition
chose "simple" or the user specified it explicitly (and the behavior
should be different).  If there were some hooks added to extend the
autorecognition within the framework rather than working around it, I'd go
so far as to say that it isn't SysV spooler that sucks, but anything else.

The real problem IM (honest but _never_ humble) O is that damn near
nobody seems to take the trouble to _understand_ the SysV spooler, not
that the documentation, which does suck (and omits some things, like the
mapping of certain lpr options to filter names, last I checked [but I have
the source from when it was readily available, although have only used
it to further understand, not to modify]) helps much.

-- 
mailto:rlhamil@mindwarp.smart.net  http://www.smart.net/~rlhamil

Richard.L.Hamilton@mindwarp.smart.net (Richard L. Hamilton) writes:
>In article <bkfkk0$bph$2@anubis.demon.co.uk>,
>	huge@ukmisc.org.uk (Huge) writes:
>> "Kevin" <news@tnet.com> writes:
>>>
>>>"cvreddy5" <member40387@dbforums.com> wrote in message
>>>news:3390608.1063982172@dbforums.com...
>>>>
>>>> Hi
>>>>
>>>>
>>>>
>>>> I installed cups on solaris 8 successfully and able to give print on my
>>>> line printer.
>>>
>>>Maybe that is what caused your posting to be so messed up too?  All the
>>>extra line spacing?
>>>
>>>Why would you want to use Cups in the first place?
>> 
>> Because the SysV print spooler sucks donkey d*ck?
>
>How so?  I've gotten it to do everything I've ever wanted, albeit with
>some work.
 ^^^^^^^^^

Precisely. When we upgraded from Solaris 1 to Solaris 2, we had such
trouble getting the Sol 2 spooling system to work properly, we kept a
Sol 1 machine hanging around just to do print spooling.

I wouldn't touch it with a sh*tty stick.

-- 
       "The road to Paradise is through Intercourse."
The uk.transport FAQ; http://www.huge.org.uk/transport/FAQ.html
        [email me at huge [at] huge [dot] org [dot] uk]

Huge wrote:
> Precisely. When we upgraded from Solaris 1 to Solaris 2, we had such
> trouble getting the Sol 2 spooling system to work properly, we kept a
> Sol 1 machine hanging around just to do print spooling.

Well, first of all, back then the SysV-style spooling system had bugs
and it was genuinely hard to get it work right.

Second, lpd and /etc/printcap are so vastly different from it that
it takes some time to adjust.  Particularly because the documentation
is a bit sparse.  But once you do adjust, you actually begin to
understand that the SysV spooling system isn't that complex
and furthermore has some handy features.

For instance, with /etc/printcap you have to specify explicitly
how to translate from every possible input format to the one
accepted by the printer, and that has to be done separately
for each printer.  The SysV style stuff lets you just say
"this is how to translate text to postscript" one time, in one
place, and you're done.

Unfortunately, it still doesn't (as far as I know) let you say
"this is how you can tell that a file is postscript"[1], which is
a shame, because if you could do that, I'd have my print system
accepting JPG, PNG, GIF, PDF, PS, text, .gz, .Z., .bz2, and
probably more.

   - Logan

[1]  As I understand it, it does recognize several file types,
      but the logic to do so is hard-coded.

On Sat, 20 Sep 2003 18:22:15 +0000, Logan Shaw wrote:

> Unfortunately, it still doesn't (as far as I know) let you say
> "this is how you can tell that a file is postscript"[1], which is
> a shame, because if you could do that, I'd have my print system
> accepting JPG, PNG, GIF, PDF, PS, text, .gz, .Z., .bz2, and
> probably more.

I removed the SysV printing system from a Solaris x86 server, installed
LPRng, which uses /etc/printcap, and then installed apsfilter.  The filter
can accept all of those file types, convert them to postscript then pass
the stream to ghostscript to translate the PS to the format required by an
HP printer.

Logan Shaw <lshaw-usenet@austin.rr.com> writes:
>
>Unfortunately, it still doesn't (as far as I know) let you say
>"this is how you can tell that a file is postscript"[1], which is
>a shame, because if you could do that, I'd have my print system
>accepting JPG, PNG, GIF, PDF, PS, text, .gz, .Z., .bz2, and
>probably more.
>
>[1]  As I understand it, it does recognize several file types,
>      but the logic to do so is hard-coded.
>

Based on the old SVR4.0 code that I've seen, the autodetection
doesn't support any file types besides Postscript and simple (text).
The rest of the file types must be specified by the user with the
-T option to the lp command.

Perhaps autodetection was changed in SVR4.2?

  -Greg
-- 
Do NOT reply via e-mail.
Reply in the newsgroup.

cvreddy5 <member40387@dbforums.com> wrote in news:3390608.1063982172
@dbforums.com:

> 
> Hi
> 
> 
> 
> I installed cups on solaris 8 successfully and able to give print on my
> line printer.
> 
> 
> 
>   The problem is /opt/sfw/cups/var/log/cups/page_log is not giving me
>   the right count of number of pages given by the user.
> 
> 
> 
>  $> cat page_log
> 
> 
> 
> printer root 1 [16/Sep/2003:09:15:19 +0500] 1 1
> 
> printer test 2 [16/Sep/2003:09:29:48 +0500] 1 1
> 
> 
.....
.....

hi

your print jobs are postscript files - right ?
then it might happen, that your files are non dsc compliant. what means 
they have a showpage command in the ps file (which call a form feed for 
the printer) but actually there's no page counting for the printing 
system.  to check if this is the case view your printfiles in ghostview 
(on pc or sun, doesn't matter). if you can go forward and backward, the 
problem is another on. if the file is not dsc compliant you may go one 
page forward but not back.
if this is true, you can filter your files with ghostscript (pswrite) and 
try again.  if the page_log is correct then, you could add an additional 
filter to cups, which converts any non dsc files to dsc files .
adding an own filter to cups is quite easy, its just a simple shell 
script.

anyway i'd recommend upgrading to the professional version of cups ESP 
print pro - tons of drivers and a nice gui.

cheers

robert



-- 
________________________________________
  Robert Gruener - rgruener @ online.de
________________________________________