When running a Unix Report Server, if you issue the command: ps -ef | grep iq, you will notice that you have processes for something called windu. This document explains what those processes are and what they do.
You will notice that after the iqverify has completed, there are some new processes running (i.e. windu_clientd42 and windu_registryd42):
What are the processes windu_clientd42 and windu_registryd42 used for?These are Wind U daemons. You will see these after iqverify runs. This is because iqverify calls the iqserver executable. These daemons provide some of the things that are built into NT and accessed differently on UNIX like registry entries, fonts, display, and printer information.
$ ps -fu iass | sort
UID PID PPID C STIME TTY TIME COMMAND
iass 24571 6399 0 15:23:56 ttyr2 0:00 -ksh
iass 24644 1 0 15:25:35 ttyp6 0:00 iqjobsrv
iass 24650 1 12 15:25:37 ttyp6 0:00 iqmonitr
iass 24653 1 0 15:25:37 ttyp6 0:00 iqwpsrv
iass 25470 1 0 15:35:41 ttyq4 0:00 windu_clientd42 -display
iass 25472 1 0 15:35:43 ? 0:00 windu_registryd42 -vers 2
-prog 805503080 -d /opt/reportwrit
iass 24655 24587 5 15:25:50 ttyp6 0:00 ps -fu iass
The Wind/U registry daemon manages communication between applications and the registration database. It has the following names and syntax: In the Microsoft Windows environment, the registration database used by applications is built into the operating system. UNIX operating systems, however, do not provide this feature. Therefore, Wind/U provides windu_registryd42 to manage communication between applications and the registration database. The windu_registryd42 registry daemon manages communication between applications and the registration database windu_reg.dat. Registry APIs in your application access the registration database via this daemon.
The Wind/U client daemon manages shared color X resources for all Wind/U applications on a single X server. It has the following name:windu_clientd44 Wind/U automatically starts windu_clientd44 when a Wind/U application starts, if it is not already running. It has the same DISPLAY setting as the application. In Windows, certain static colors always stay on certain index positions by default. For example, black is always index 0 and white is index 255 on a 256-color display. Certain Windows ROPs depend on these fixed index locations. In X Windows, however, you cannot make the same index position assumptions. The windu_clientd44 daemon attempts to reserve index positions for certain colors so that these ROPs work correctly across platforms. It also enables those color cells to be shared by all Wind/U applications on adisplay, reducing color resource consumption. This daemon is intended for use with non-palette mode (the default mode). In palette mode (used when a private colormap is needed), Wind/U uses windu_clientd44 if it can be started to reduce technicolor (moving the focus out of your application causes the colors in your application to go wrong). Wind/U applications still run fine without the daemon, but you may notice some color flickering, especially if you are running several Wind/U applications, because Wind/U runs in palette mode if without the daemon. The windu_clientd44 daemon is only used for 8-bit pseudo-color displays. It is not needed and will not start for 24-bit displays. If you see more than one daemon running on a system, they are running on different displays. When the daemon starts, it attempts to reserve 16 system colors; if it is unable to do so, it exits. Each display requires one windu_clientd44 daemon, which reserves the 16 colors for all Wind/U applications on that display. When you distribute your application to your customers, you must distribute windu_clientd44 along with your application to ensure proper color resource management.