Tutorials

h1. Move a server to another system user

On GNUlinux, the installation recommend (!) to be root to install the server. Often, the server inherit the same rights ... This is *very* dangerous ! You should put the Scol server under a _normal_ system user.

Moreover, this will be easier and more secure to upload files and other resources to the server.

However, if the server is already installed, you can follow this tutorial (for a Debian system, but you could adapt it easely for another GNU/Linux system).

+Note+ : For a FreeBSD system, you should read this "tutorial":http://iri3d.free.fr/Docs/scs_scol/scolFbsdHT.html

# Connect you to the server machine (via SSH by example) :

<pre>

$ ssh my_user@123.456.789.012

</pre>

# Save your current Scol directory (backup)

# Create a new system user

3.1. Log in you in _root_ (or other user with sufficient rights)

<pre>$ su -</pre>

3.2. Create a simple user

<pre>$ adduser new_user</pre>

Note : you can pass any argument to _adduser_ like _-disabled-password_. This forbids _new_user_ to connect except by SSH and RSA key. For more informations, enter in your terminal : <pre>$ man adduser</pre>

# Create a new group, like _new_group_ with the command <pre>$ addgroup new_group</pre> Put _new_user_ in _new_group_.

# Copy (or move) the current Scol directory in the _new_user_ directory (typically _/home/new_user/_)

<pre>$ cp -R -v /root/scol /home/new_user/scol</pre>

The option -v is optional. It displays informations on the current operations.

# Modify the rights on _/home/new_user/scol_ to _new_user

<pre>$ cd /home/new_user

$ chown -R -v new_user:new_group scol</pre>

# Edit the file _/home/nex_user/scol/usm.ini_ (with nano by example)

<pre>$ nano scol/usm.ini</pre>

Modify the _masteruser_ value (by default, at the last line)

<pre>$masteruser new_user</pre>

Close nano with CTRL+X, Confirm the change to press Y and the same save path name with Enter

# If any, remove or modify the _start / close_ script (see [[Server 4 start and close]])

# If running, close the server

<pre>$ killall -TERM usmunix</pre>

# Start the server (from _new_user_)

<pre>$ su new_user

$ cd scol

$ nohup ./startscol.sh &</pre>

# Check if all is ok

11.1 From a client machine, connect you on <pre>http://ip_du_serveur:1199/</pre>

You should read a list of opened applications (or an empty list, if no applications uploaded)

11.2 Always from a client machine, connect you on <pre>http://ip_du_serveur:1201/CC/</pre> to configure the Scol server

# If all is ok, you can remove the old Scol directory

<pre>$ exit

$ su -

$ rm -rf /root/scol/

$ rmdir /root/scol</pre>

Be careful with the _rm -rf_ command, you can damage your system if you do a mistake.

# Log out you

<pre>$ exit

$ exit</pre>

If you want, you can adapt this script to start and close the server : [[Server 4 start and close]]

You can upload and update your resources files via SFTP (ssh + ftp), a better way than ftp only. See the OpenSSH project for more informations.