Read the notes for your OS in section System-dependent notes for specific installation help (if any).
The following is a list of commonly encountered problems and their solution. If these do not solve your problem, then send mail to the lprng@lprng.com mailing list. You will have to subscribe to the list in order to post to the list.
Make complains about a malformed make or Makefile file, illegal syntax in the file, or illegal entries in the file. You are most likely not running GNU Make. You must use GNU make or you should be a Unix Wizard able to master the mysteries of converting GNU Makefiles to your local system make. It is easier to simply install GNU make.
The C Compiler complains about missing files or has a large number of errors. Use gcc instead of your vendor's C compiler.
If there are messages about missing system files, then you most likely have an incomplete set of system include files, or the include do not properly reference other required include files, or the include files are located in an unusual location. If you are using gcc then make sure that the gcc was carried out correctly on your system. The easiest way to assure this is to recompile and reinstall the gcc compiler.
If you have checked your compiler installation and are still missing libraries or files then the include files may be in /usr/local/include and libraries may be in /usr/local/include and these directories may not searched or used by the compiler by default. This can be fixed by using the --with-cppopts= and --with-ldopts= configure options.
The software compiles but will not run on the system. Make sure that you have followed your system specific rules for compiling and installing setuid ROOT programs on your system. You may need to statically link your executables.
The software was compiled on one system and copied to another system, but will not run on the other system. Try compiling the software on the target system. If it compiles and runs, then you most likely have an issue with libraries or Operating System Versions.
After you have installed the LPRng software and rebooted your system, do the following commands:
If you do not get status displayed, or you get some other error message, then the following are a series of tests can use to check that LPRng is installed correctly.
First we will run lpd in the foreground and are used to make sure that our system configuration is correct. You will need root permissions to do the following steps. Stop the running currently running lpd process. Next, run lpd in foreground mode:
h4: {17} # ps -aux | grep lpd
daemon 240 0.0 0.0 1292 0 ?? IWs - 0:00.00 lpd: lpd Waiting
h4: {18} # kill 240
h4: {19} # checkpc -f
h4: {20} # /usr/local/bin/lpd -F -D1
Fatal error - Another print spooler is using TCP printer port
If you get the above error message, then you have either not terminated the running lpd server, there is another process using TCP/IP port 515, or you are not starting the lpd server as ROOT. See the System Specific Notes for details on how to resolve these issues.
Correct the problem and then restart the server. You should see the output indicated below:
h4: {21} # /usr/local/bin/lpd -F -D1
1999-04-05-14:35:14.023 astart27 [2667] Waiting lpd: LOOP START
1999-04-05-14:35:14.024 astart27 [2667] Waiting Get_max_servers: \
getrlimit returns 256
1999-04-05-14:35:14.024 astart27 [2667] Waiting Get_max_servers: \
returning 128
1999-04-05-14:35:14.025 astart27 [2667] Waiting lpd: \
max_servers 128, active 0
1999-04-05-14:35:14.025 astart27 [2667] Waiting lpd: \
starting select timeout 'yes', 600 sec
Now from another window do the following commands:
At this point your LPRng software has been installed and tested. See the Updating Print Spooler Software and Startup Scripts for details on how to automatically start lpd at boot time.