Solaris 2.4 printing with dpost (page length problem)

Solaris 2.4 printing with dpost (page length problem)

Post by Don Charles Lundel » Wed, 15 Mar 1995 05:29:07


I'm printing to an HP postscript printer using
dpost on Solaris 2.4.  It works fine, except
the default page length is a little longer than
11 inches (I lose a couple of lines in between pages).
I can put a .pl command in every troff document, but
I'd like to know if there's a global way to solve the
problem (command in a prologue file?).


- Don


1. Severe paging problem in Solaris 2.4

We are experiencing extremely high paging rates on our Solaris 2.4 system.
It is a Sparc5 with 32MB of RAM.  It is connected to an Ethernet network
with minimal traffic.  With two users on the system (one using OpenWindows
on the console, one connected via telnet), the system performance goes out
the window:

  1) Telnet user is running 'make', which uses 'gcc' to compile
     code --- full compilation in about 20 directories takes
     under 5 minutes.

  2) OpenWindows user just has a shell window open.  His response
     time is horrendous, with delays of several seconds.

Running "vmstat 1" shows extremely high paging rates, with "pi" and "po"
both averaging somewhere over 800.  If the OpenWindows user logs off,
these paging rates go down close to 0, even during the 'make'.

Similarly, with six progams in the background, all of them idle, but all
with 500K of private shared memory mapped in, paging rates during the
'make' are very high.  If the six programs are terminated, the paging
level goes back down.  The shared memory is not marked as "locked", so
this really doesn't make sense.

Similar tests on a SunOS 4.1.3 system with the same hardware do not
exhibit this heavy paging behaviour.

As I said, there is 32MB of RAM on the system.  During these tests, it
appears that about 20MB of swap space is reserved (there is over 100MB
of swap space on the system).  Theoretically, the paging could be stopped
by going up to 64MB of RAM, but the activities on this system should be
able to work properly in just 32MB of RAM, and that in fact seems to
be the case on the 4.1.3 system.

Does anybody know of any problems with 2.4 that might be causing this?
Are there any parameters I can examine or tune to help determine the
cause of the heavy paging?  I know that HP-UX 9.x systems had a problem
with dynamic buffer cacheing, which exhibited similar symptoms, but I have
not yet found a way to determine how much memory is being used by
Solaris's buffer cache, and I don't know if something similar is happening

If possible, e-mail any responses in addition to posting --- our news
feed has been a bit flaky the last few days.


2. Bridge + Firewall: question about IPs and routing.

3. Path length limit on Solaris 2.4?

4. A question on FIFOs

5. Printing Question. double sided printing on Solaris 2.4

6. atime-patch again...

7. Solaris 2.4: Sendmail throws out Content-Length

8. routing problem(s) ....

9. HP-4M Solaris 2.4 Printing Problems

10. Printing Problem - Solaris 2.4

11. Problem of Solaris 2.4 printing with Line Printer Daemon

12. Printing problems between Solaris 2.4 and Windows NT

13. Solaris 2.4 NFS printing problems