When tlclient starts, it attempts to extract the pid from the first line of the previous log file (generally ~/.thinlinc/tlclient.log) to know which process created the file.
This behavior is somewhat problematic as pid's are not unique across system restarts and are generally sequentially generated.
A possible problematic scenario with this approach is if the log file gets associated with a very low pid if tlclient is run directly after system startup. If a number of system services are installed after this first tlclient startup, we run the risk of these services occupying the previous tlclient pid on subsequent system startups, resulting in the original client log file never being removed.
Ideally, we would also like to check that the pid in the log file actually belongs to a tlclient process before we rotate or something similar.