Records the time, as an integer timestamp, this remote-access user's session logged on. This is what an admin uses to spot anomalously long-lived sessions; a raLogonTime far older than any reasonable workday length for a user who's supposedly still active can indicate a session that never properly torn down and is quietly consuming a license slot or a connection-table entry. Example: a session showing raLogonTime from four days ago while raUserState still reports active(3) is a strong candidate for a stale session that should be forcibly cleared.