Default Setting: OPT_LOGINUSR='no'
OPT_LOGINUSR='yes': use true login (recommended)
LOGINUSR provides a true login (User/Password). Account management is done in the config file, passwords will be transferred only encrypted.
LOGINUSR_DELETE_PERSISTENT_DATA
User data on a harddisk will survive reboots.
The deault setting 'no' only preserves Account data.
With specifying 'yes' here all user accounts will be deleted on every reboot.
Afterwards they will be recreated as described below.
It is recommended to keep the 'no' here to preserve all account data, i.e.:
LOGINUSR_ACCOUNT_N='0'
LOGINUSR_ACCOUNT_N
The number of accounts defined.
LOGINUSR_ACCOUNT_x_USER='user1'
LOGINUSR_ACCOUNT_x_USER
Username for login (mandatory).
LOGINUSR_ACCOUNT_x_PWD='user1_secret'
LOGINUSR_ACCOUNT_x_PWD
Password for login (mandatory)
LOGINUSR_ACCOUNT_x_FORENAME='Vorname'
LOGINUSR_ACCOUNT_x_FORENAME
First name of the user for better management (optional, may be empty).
The content is shown in the logs and in the Admin interface to help the Admin
to better recognize users being online at the moment.
LOGINUSR_ACCOUNT_x_SURNAME='Nachname'
LOGINUSR_ACCOUNT_x_SURNAME
Last name of the user for better management (optional, may be empty).
The content is shown in the logs and in the Admin interface to help the Admin
to better recognize users being online at the moment.
LOGINUSR_ACCOUNT_x_EMAIL='usr1@home.de'
LOGINUSR_ACCOUNT_x_EMAIL
E-Mail of the user for better management (optional, may be empty).
The content is shown in the logs and in the Admin interface to help the Admin
to better recognize users being online at the moment.
LOGINUSR_ACCOUNT_x_OVERWRITE='yes'
Optional:LOGINUSR_ACCOUNT_x_OVERWRITE
Overwrite persistent user data on system restart.
A directoy for persistent data storing may be specified here to hold account data. This way the data is preserved after a reboot. With this option user accounts and all data for them (statistics) may be overwritten.
LOGINUSR_ACCOUNT_x_TIME='60'
Time amount solely for this user, defined in minutes.
If omitted, C3SURF_TIME is valid. Overwriting only makes sense if C3SURF_QUOTA='yes' has been defined.
LOGINUSR_ACCOUNT_x_BLOCKTIME='240'
Locking time solely for this user.
If omitted, C3SURF_BLOCKTIME is valid. Overwriting only makes sense if C3SURF_QUOTA='yes' has been defined.
LOGINUSR_ACCOUNT_x_COUNTER='1'
Number of logins solely for this user.
If omitted, C3SURF_COUNTER is valid. Overwriting only makes sense if C3SURF_QUOTA='yes' has been defined.
LOGINUSR_ACCOUNT_x_CURFEW='List of curfews'
Format: (List of curfews 0-23 separated by spaces)
Example: LOGINUSR_ACCOUNT_x_CURFEW='0 1 2 3 4 5 6 7 21 22 23'Meaning: A login is allowed only between 8:00-20:59. The login will always be denied if the user tries to login within the hour in the list (plus 0-59 minutes).
If the user is logged in and runs into a curfew, he will be logged out without a warning. The logout behavior can be prevented by specifying C3SURF_CHECK_CURFEW='no'.
By using this list access can be restricted very flexible. The list can also be managed in the Web interface. No checking of the list is performed.
Only the numbers from 0 to 23 make sense!
OPT_C3SURF Parameters belonging here:
C3SURF_CHECK_CURFEW='no'