AppSuite:Logincounter: Difference between revisions
From Open-Xchange
Line 1: | Line 1: | ||
= Login Counter = | |||
Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the *last* login of a specific user with a specific client. This data can be displayed with the <code>logincounter</code> tool. | |||
The clients provided by Open-Xchange use the following client identification strings: | |||
== Using the <code>logincounter</code> tool == | == Using the <code>logincounter</code> tool == | ||
Revision as of 14:50, 19 May 2014
Login Counter
Whenever a user is logged in through the login servlet, the context id, user id, client identification string and a time stamp is saved to the database. If a database entry for this combination of context, user and client is already present, only the timestamp is updated. This means that the database holds the information for the *last* login of a specific user with a specific client. This data can be displayed with the logincounter
tool.
The clients provided by Open-Xchange use the following client identification strings:
Using the logincounter
tool
# logincounter --help usage: logincounter -a,--aggregate Optional. Aggregates the counts by users. Only the total number of logins without duplicate counts (caused by multiple clients per user) is returned. -e,--end <arg> Required. Sets the end date for the detecting range. Example: 2010-01-1 23:59:59 -h,--help Prints a help text -r,--regex <arg> Optional. Limits the counter to login devices that match regex. -s,--start <arg> Required. Sets the start date for the detecting range. Example: 2009-12-31 00:00:00