| 134 | |
| 135 | === Starting the services === |
| 136 | |
| 137 | To start SALI initiate the following: |
| 138 | {{{ |
| 139 | /etc/init.d/sali start |
| 140 | }}} |
| 141 | |
| 142 | This will not start the `rsync` server. For this you must use the rsync init script supplied by your distribution. For example debian: |
| 143 | {{{ |
| 144 | sali rsync |
| 145 | /etc/init.d/rsync start |
| 146 | }}} |
| 147 | |
| 148 | The `sali rsync` command will generate a rsyncd.conf file in `/etc/rsyncd.conf`. If you want to save the rsyncd.conf in a different location adjust the `/etc/sali/sali.cfg` file. |
| 149 | |
| 150 | === Checking if SALI is running === |
| 151 | |
| 152 | First check on what the PID number is of the `sali_server` process: |
| 153 | {{{ |
| 154 | # ps -ef|grep sali_serverroot 2952 1 0 Jan26 ? 00:44:19 /usr/bin/python /usr/sbin/sali_server /etc/sali/sali.cfg star |
| 155 | }}} |
| 156 | |
| 157 | And with the command `lsof` we can check on which ports `sali_server` is listening: |
| 158 | {{{ |
| 159 | # lsof -p 2952 | egrep "TCP|UDP" |
| 160 | python 2952 root 13u IPv4 10559 0t0 TCP *:8181 (LISTEN) |
| 161 | python 2952 root 17u IPv4 10560 0t0 TCP *:6969 (LISTEN) |
| 162 | python 2952 root 18u IPv4 10567 0t0 TCP *:22456 (LISTEN) |
| 163 | }}} |