File Permissions and OS Specific Notes

• Windows IIS will typically run texis.exe as the anonymous user IUSR_machine. If you want searches to automatically recompile scripts for you, then this user will need write permission on the directories containing the scripts: texis/scripts/webinator.

  Another option is to test and compile the scripts in a staging area, and when you are satisfied with the results, simply move the compiled .vsc file into place.

  Texis requires that its monitor process is running. It will attempt to start it if it's not already running. When Texis is running under the web server, there might not be permission available for it to run properly. As administrator, you can register the Texis monitor as a service to run in background and when the system starts up. The install will do this if run as an administrator. You can do this manually from a command prompt when logged in as administrator:

  monitor -R

  This will start the monitor service immediately, so there's no need to reboot to activate it.

  If you ever wish to unregister the Texis monitor as a service, do this from a command prompt when logged in as administrator:

  monitor -U

• Unix It is important that texis and its related utility programs always run as the same userid, and that that userid is the owner of the databases. Web servers generally run CGI programs as some user with little or no permission. The installation attempts to get around this problem by making the programs setuid to the correct user. If it is not able, you will receive a warning. It is up to you to ensure that texis is always run as the same userid.

  The standard Unix commands for making a program setuid to some user, myself for example, are:

  chown myself texis
  chmod u+s texis

  The above commands may only be run by the root user on some systems.