In some circumstances, it may not be convenient to run ScaleOut StateServer as a service (daemon). For example, running as a service requires root privileges, which may not be available. Also, you may need to run ScaleOut StateServer out of a different directory from its default installation directory.
You can run ScaleOut StateServer from the command line as a "command-line daemon" instead of as a system service, as follows:
- First, create a directory for running ScaleOut StateServer.
-
Copy both parameters files (soss_params.txt and soss_client_params.txt) to this directory and create a symbolic link to the sossd executable program, for example:
cp /usr/local/etc/soss_params.txt . cp /usr/local/etc/soss_client_params.txt . ln -s /usr/local/bin/sossd .
- Set the SOSS_HOME environment variable to that directory’s path.
-
Run sossd with the -d flag in the background, for example:
./sossd -d &
When the StateServer service starts, it will print some initial messages to stdout before it becomes a daemon. Throughout its operation, it will also create trace log files in the directory specified by SOSS_HOME instead of in /var/log/soss.
Note | |
---|---|
When sossd is run by a non-root user (or on Linux, any user without CAP_SYS_NICE), it will be unable to elevate certain important threads above normal priority. This may cause stability issues due to lack of responsiveness under very high CPU load. It should not be a problem under most circumstances. |