Server Log Warning #8681 server was unable to chmod (not owner?)

If you receive a server log warning #8681 server was unable to chmod <filename>, this is normal behavior. The study server tries to protect the study files by making them read only when it isnot writing to them, but it can’t do that if the study server was started by a user who is notthe owner of the study files. You get that warning message when the server is not the owner.

Since the implementation of the safe versions of rm, cp, and mv, it is much less important as theSurvox safe scriptswhich are typicallyinstalled as part of the installation process protects those files as well. Many of our users set the umask to 000 for the login script of the user or cron that starts up the studyserver to make sure that the studyserver has complete control over those files when being utilized for production use. Although from a security perspective umask 000 isin most casesforbiddenby many systemAdminsas it can allow full read write access to files after they have been released by the studyserver.

You can find more information regarding the permissions on files below or on theSurvox Distribution website under the software setup page at

Recommended Structure ofSurvox UNIX Site

NOTE:Please see the files login.exam and cshrc.exam in the control sub-directory of your mainSurvox software directory for more detail on recommended c-shell environment settings.

Minimum Hardware Requirements:

  • A reasonably contemporary CPU (e.g., one that has a Pentium chip). At least 128 MB of RAM (estimate about 2.5 megabytes per WebSurvent session).
  • 10 GB partition on hard drive devoted toSurvox applications (/cfmc). 10 gigabytes is actually more than enough. If it is not possible to make a partition, install in a partition other than root. The reasoning behind this is if you fill up the disk using our software, you’ll only crash our software, not the machine.
    NOTE: DO NOT install the software on a network-mounted partition, there may be file locking problems that we cannot avoid.
  • Fast Internet Connection – T1, if possible. (3com network cards are preferred. They seem to have fewer traffic problems.)
  • Telnet/ssh capabilities or a dedicated modem (for troubleshooting)

Setting up users:
The preferred command interpreter is /bin/tcsh (c-shell). If this is not available, /bin/csh will suffice. In any case, c-shell is the only shell we really know and can support you with.

.login highlights:
umask 000
setenv CFMC <wherever the software was installed>/
(e.g., “setenv CFMC /cfmc/”, the last “/” is far too important)
setenv CFMCCFG ${CFMC}ipcfiles/
setenv PATH .:/bin:/usr/bin:/usr/local/bin/:${CFMC}go/

The path can include anything desired, just make sure that ${CFMC}go/ is included
$CFMC is used widely in the software to define where to look for particular functional files necessary to run the software
$CFMCCFG defines where to look for necessary communication files.
The PATH allows you to run any of the programs in the ${CFMC}go/ directory from any other directory.

NOTE: NEVER run ANYSurvox programs while situated in the ${CFMC}go/ directory.

NOTE: See ${CFMC}control/login.exam for more detail

User Types:

User Name Description Group
cfmc software owner cfmc
server study server cfmc
super supervisor cfmc
If using telnet/ssh sessions (i.e. non-hardwired):
User Name Description Group
intv### interviewers <not cfmc>
code### coders cfmc
If using hardwired terminals:
User Name Description Group
intv interviewers <not cfmc>
code coders cfmc
Others (any user name)
Description Group
spec writer cfmc
unsupervised cfmc

### for telnet/ssh interviewer and coder accounts:
Specify the station number/ldev in the signon name (e.g., intv101) and put the following in .login:
setenv LDEV `echo $LOGNAME