For security reasons, RSM will not allow any job to be run by the "root" user on Linux, including primary and alternate accounts.

It may sometimes be necessary for you to enter the full path to the solver executable file in the Solve Process Settings.

It may sometimes be necessary for you to enter the full path to the Linux working directory in the Linux Working Folder field of the Solve Process Settings.

The LSF administrator should configure the Workbench job server to disallow multiple, simultaneous jobs. Two solves running on the same server will interfere with each other, preventing successful completion of each.

To help in debugging solver startup problems on the remote machine, it is sometimes useful for you to use the Solution Information object under the Solution object in the tree. The Solution Information object will show the contents of the solve.out file that the remote solver produced, if the application was able to start.

When using the Stop Solution option to stop a solve running on a Linux machine, it is possible that the solver will continue to run on that machine even though the Mechanical application thinks it has stopped. If this happens and you don't want the solve job to continue on the Linux machine it will be necessary for you to kill the process manually. The ability to solve to two different Linux machines simultaneously is not allowed.

The solve command may have failed to execute on the remote Linux server. Verify the command's spelling and/or path. Solve commands are issued to the remote server using the rexec interface. Failures may occur if the resulting path ($path) is insufficient. $path can be verified by issuing rexec on the command prompt on the local machine. For example:

rexec machinename -l username echo $path > diagnosticsfile

(where "l" is the letter "el)"

The machinename and username match the entries in the Solve Process Settings, and diagnosticsfile corresponds to the recipient on the local machine for the command output.

If the path to the solve command is unavailable on the remote server, it can be added to user or system-wide files that initialize the startup shell (for example, .cshrc or /etc/csh.login on C-shells). Consult the Linux server's rexec interface and appropriate shell manual pages for details.

If you cannot make ASCII transfers to a Linux server, changes need to be made on the server. Background solutions on a remote Linux server use file transfer protocol (ftp). Therefore, the system administrator must install ftp and enable it. Ftp uses ASCII transfer mode to convert PC text to Linux text. If ASCII mode is disabled, it is not obvious because error messages do not imply this. On some ftp servers (vsftpd, for example), by default, the server will pretend to allow ASCII mode, but in fact, will ignore the request. You will need to ensure that the ASCII upload and download options are enabled to have the server actually do ASCII mangling on files when in ASCII mode. To enable these options, the system administrator should consult the operating system documentation. The following vsftp.conf modification procedure is Linux platform specific and is provided as an example only.