Manual TCIP 603-03 TCIP SRV 603-0 - Siedle

Manual TCIP 603-03
5.6. Server behaviour
Task
• All failed tasks are automatically restarted (e.g. if the TCIP 603-... cannot be reached when creating a user).
• If a task could not be correctly executed, the system attempts to execute the task again with every start of the scheduler
until it has been either executed or deleted.
• The task list is configured in such a way that after an error executing a task, all subsequent tasks on the same TCIP are
suspended to prevent confusing the sequence. For this reason, it is advisable to check the task list at regular intervals. The
last current status is displayed in the page header.
5.7. Users in the TCIP
The first 500 stored users are saved in the local TCIP in the sequence in which they were stored. All users with fingerprint
data are stored locally. Depending on the access group, however, deviations from this procedure can occur, i.e. the
number of users which can be managed locally on the TCIP 603-... does not need to be identical, nor does it need to be
equal to 500.
5.8. Resetting the TCIP server to the default settings
A complete copy of the Siedle server application is located on the server. This can replace the working version if required.
This will completely wipe the user database. Linux-specific settings such as IP address or NTP server settings are not
changed as a result.
The user‘s own inputs are shown in the following in bold type.
Log in directly at the server
TCIP-S login: Service
Password: Siedle
Change to the folder “home/Service/siedle/“ with cd siedle
Access the script ./i-script.sh
The sequence of individual script commands is subsequently documented. After completion of the script, the system must
be rebooted. This can be initiated with the following command:
Service@TCIP-S:~/siedle$ sudo reboot
Password: Siedle
51