| Features | | Download | | License | | Purchase | | Support | | Manual |
|
Here you will find the most frequent questions that arise while installing pssRecruit and some initial users' issues. pssRecruit runs on a wide variety of platforms with an even wider variety of configurations. We provide free e-mail support for our products and can resolve most configuration problems. If you are experiencing a problem not listed here, let us know. |
You must select Binary mode. If you do not select Binary mode, pssRecruit will not run on your Webserver.Go Back to the Question
When executed, pssRecruit creates a temporary file in directory that pssRecruit is located. This error will ocurr if you have the directory where pssRecruit executable resides set as "Read Only" from the NTFS or unix file system perspective. Additionally, in an NT environment, a temporary file is also created in directory defined by "TEMP". In a W2000 environment, a temporary file is created in the Winnt\Temp directory. When execution is completed, temporary files are deleted. Consequently whoever "owns" the pssRecruit application needs write access to its corresponding directory. In an NT/2000 environment this user is usually IUSR_System_Name. In a 2000 environment, one must explicitly add this write access to the Winnt\Temp directory. In the NT/2000 enviroment: Right click on the directory, select Properties, Security, Permissions to add write access to the owner of pssRecruit process. [In an IIS environment one does NOT need to enable write access from the IIS admin GUI. Script/Execute access is the only box that should be checked!]Go Back to the Question
This error will ocurr if you have the directory where pssRecruit executable resides set as "Read Only" from the NTFS or unix file system perspective. Additionally, in an NT environment, a temporary file is also created in directory defined by "TEMP". In a W2000 environment, a temporary file is created in the Winnt\Temp directory. When execution is completed, temporary files are deleted. Consequently whoever "owns" the pssRecruit application needs write access to its corresponding directory. In an NT/2000 environment this user is usually IUSR_System_Name. In a 2000 environment, one must explicitly add this write access to the Winnt\Temp directory. In the NT/2000 enviroment: Right click on the directory, select Properties, Security, Permissions to add write access to the owner of pssRecruit process. [In an IIS environment one does NOT need to enable write access from the IIS admin GUI. Script/Execute access is the only box that should be checked!]Go Back to the Question
From a command prompt, run the three commands listed below on the Webserver on which you intend to run pssRecruit. Mail the output to support@progressivesoft.com. PSS will send you a compiled version of pssRecruit that will work on your platform. Please note that the last command is not in single quotes--the command itself includes the back ticks (the key left of the "1" key on many keyboards). The three commands follow:Go Back to the Questionstrings pssRecruit.cgi | grep lib ls -l /lib /usr/lib ldd `which perl`
We are a small company located in Alexandria, VA. Yes, pssRecruit was made in America! But, our reach is global with satisfied customers on six continents.Go Back to the Question
Yes pssRecruit is readily customized. For samples with source code to customize your pssRecruit interface, please goto http://www.progressivesoft.com/PR-Custom/PR-Customize.shtmlGo Back to the Question
From a command prompt, run the command listed below on the Webserver on which you intend to run pssRecruit.Go Back to the Question
Mail the output to support@progressivesoft.com.
PSS will determine if we can send you a compiled version of pssRecruit that will work on your platform.
Please note that the command is not in single quotes--the command itself includes the back ticks (the key left of the "1" key on many keyboards). The command follows:
ldd `which perl`
For redhat Linux:Go Back to the Questionlibnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.6 => /lib/libc.so.6 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Slackware Linux:libnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.5 => /lib/libc.so.5 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Caldera Linux:libnsl.so.1 => /lib/libnsl.so.1 (0x40015000) libdl.so.2 => /lib/libdl.so.2 (0x4002c000) libm.so.6 => /lib/libm.so.6 (0x4002f000) libc.so.5 => /lib/libc.so.5 (0x4004b000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4013e000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) For Cobalt Linux:libnsl.so.1 => /lib/libnsl.so.1 (0xcaacd000) libdb.so.2 => /lib/libdb.so.2 (0xcab14000) libdl.so.2 => /lib/libdl.so.2 (0xcab67000) libm.so.6 => /lib/libm.so.6 (0xcaba9000) libc.so.6 => /lib/libc.so.6 (0xcac0d000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xcad22000) /lib/ld.so.1 => /lib/ld.so.1 (0x00000000) For FreeBSD:libperl.so.3 => /usr/lib/libperl.so.3 (0x28063000) libm.so.2 => /usr/lib/libm.so.2 (0x280f4000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2810f000) libc.so.3 => /usr/lib/libc.so.3 (0x28112000) For other operating systems: Please send the output to support at progressivesoft.com
The X11 lib is missing in the cgi environment on BSDOS Virtual Servers. Consequently, compiled executables do not have proper path identified in your Virtual Server environment. To correct this Virtual Server bug, you must:Go Back to the Question
1. telnet to your webserver
2. log in as the user that the webserver runs as
3. issue following commands:
a) mkdir ~/usr/X11R6
b) mkdir ~/usr/X11R6/lib
c) ln /usr/X11R6/lib/*_s.3* ~/usr/X11R6/lib
The NTFS File Permissions are set by Right clicking on the directory, select Properties, Security, Permissions, Add, Show Users, Select IUSR_xxx, Full Control. From the NTFS, perspective give IUSR_xxx the following permissions to pssRecruit directory and all subdirectories and files:Go Back to the QuestionpssRecruit (dir) READ, WRITE, EXECUTE DisciplineDefinitions.tpl READ footer.tpl READ header.tpl READ PopupHTML.tpl READ pssRecruit.adm READ, WRITE pssRecruit.exe EXECUTE pssRecruit.ini READ pssRecruit.tpl READ WelcomePageFooter.tpl READ WelcomePageHeader.tpl READ Postings (dir) READ, WRITE, DELETE Jobs1234.txt READ, WRITE, DELETE Temp Directory READ, WRITE, DELETE
The Linux / Unix File Permissions are set either by telnet-ing to the location of your pssRecruit application or by using ftp. In the example below, 'nobody' is the user/group that httpd runs as. From the Linux / Unix file system perspective give 'nobody' the following permissions to pssRecruit directory and all subdirectories and files:Go Back to the Questiondrwx--x--x 3 nobody nobody 4096 Apr 3 11:44 pssRecruit (Directory) -rw-rw-rw- 1 nobody nobody 294 Feb 24 21:09 DisciplineDefinitions.tpl -rw-rw-rw- 1 nobody nobody 163 Mar 13 21:35 PopupHTML.tpl drwxrwxrwx 2 nobody nobody 4096 Apr 3 12:58 Postings -rw-rw-rw- 1 nobody nobody 180 Mar 15 21:18 WelcomePageFooter.tpl -rw-rw-rw- 1 nobody nobody 121 Mar 15 19:57 WelcomePageHeader.tpl -rw-rw-rw- 1 nobody nobody 258 Mar 15 21:18 footer.tpl -rw-rw-rw- 1 nobody nobody 91 Feb 10 13:34 header.tpl -rw-rw-rw- 1 nobody nobody 880640 Apr 3 11:44 pr.tar -rw-rw-rw- 1 nobody nobody 66 Apr 3 12:42 pssRecruit.adm -rwxr-xr-x 1 nobody nobody 857327 Mar 19 19:44 pssRecruit.cgi -rw-rw-rw- 1 nobody nobody 6292 Apr 3 12:02 pssRecruit.ini -rw-rw-rw- 1 nobody nobody 408 Mar 15 21:20 pssRecruit.tpl -rw-rw-rw- 1 nobody nobody 314 Feb 26 14:36 readme.txt
| PSS Home | Products | Order/Prices | Support | Download | Search |
|
Copyright © 2000 - 2001 Progressive Software Solutions, LLC 11327 Anthony Hwy Waynesboro, PA 17268 US Phone: 717-762-9516 Fax: 717-762-9516 |