Manual
LCom
Page 132 of 158
5.16 File Update.txt
The “update.txt” file serves to control the update mechanism in the LCom.
The file has the following content:
Line 1: Timestamp (UCT/Unix timestamp as integer)
– where appropriate with
“readable” date after the Unix timestamp.
Line 2: Optional: The name of the “Update Command File” to be processed (see
below). If no name is specified, “update.ucmd” is assumed.
The update is processed depending on
where the “Update.txt” file is located:
a)
Update.txt in the “general” directory on the FTP server: The LCom reads the
file if it has a different “last modified” timestamp than the last time the file was
read (or if the LCom was rebooted). The timestamp in the file (first line) is
checked. If the timestamp is
“newer” (more recent) than the timestamp of the
last processed “general” update (which is stored in the LCom), the update
“command file” is downloaded and processed. After processing the update a
copy of the “command file” - with the processing timestamp and “.ERROR” (if
an error occurred) or “.OK” (if the update could be processed successfully) as
additional extension -
is stored in the “device specific” directory on the server.
This file allows to easily check the progres
s of any “general” updates for the
individual LCom.
b)
Update.txt in the “device specific” directory on the FTP server: If the file is
present this directory, the LCom always processes it, i.e. the assigned
command file is transferred and processed. After processing the update, both
the
“update.txt” and the command file are renamed on the FTP server (which
prevents multiple executions). A
timestamp and the additional ending “.OK” or
“ERROR” is appended to the filename.
c) Update.txt on the USB stick: Whenever a US
B stick containing an “update.txt”
file is plugged in, the user is prompted whether the update should be
processed or not. The dialog is automatically closed after 1 minute (without the
update being processed) if the user does not respond. The update can be
