Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028221 by RavinderSingh13 on Wednesday 2nd of January 2019 09:05:38 AM
Old 01-02-2019
Quote:
Originally Posted by Neo
Well, we don't need to invoke on login, because sometimes a user will not logout for days or weeks.
We can invoke when user views any page, but I guess the best is "showthread" because anyone who is looking at a thread, is "active"...
Regarding your badging logic, I thought you were going to write badge logic for consecutive days active, no?
Your logic seems to only count days, consecutive days or not....
Is that want you want? Just counting days? Not consecutive days?
No, I have taken care of consecutive days, if condition 2nd is NOT TRUE means (today's date - 1) != lastlogin) then it again sets daily_login_count to 1 rather than adding 1 to its count, hence taken care of consecutive thing.

Now coming to logging out logic(I have a question here), whenever we see Who is Online page then after 29 mins I see people will not be seen isn't it they are logged out now from forum(sorry till now I thought this only that user's sessions have 30 mins expiring time)?

Thanks,
R. Singh
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid: https://www.unix.com/members/1-albums215-picture991.png The prototype HTML code for this layout: <style> .fa-badge-grid { font-size: 1.5em; } .row { ... (38 Replies)
Discussion started by: Neo
38 Replies

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
userstat(1M)															      userstat(1M)

NAME
userstat - check status of local user accounts SYNOPSIS
[parm]... [parm]... DESCRIPTION
checks the status of local user accounts and reports abnormal conditions, such as account locks. If any parm arguments are specified, abnormal status is displayed only for those parameters, otherwise abnormal status is displayed for all parameters. The section describes the various parameter values that can be used for parm. Each account with an abnormal status is displayed on a single line. Each line contains the username followed by one or more parameters, indicating what abnormal conditions exist for the account. The section describes the various parameters that can be displayed. Options The following options are recognized: Display the status of all users listed in (Quiet) Do not print anything to standard output. This can be used when interested only in the return value. Check the status of only the specified user name. The user must be a local user listed in Parameters The parameters that could be displayed to indicate abnormal account status, or that could be used with the option, include the following: is displayed if an administrator lock is present on the account. This lock indicates that the encrypted password in or begins with An administrator lock can be set, for example, with is displayed if the account is locked because the account expiration date has been reached. days is the number of days that the account has been expired. See the description of the expiration field in shadow(4). is displayed if the account's password has expired. days is the number of days that the password has been expired. days is displayed only if its value can be determined. is displayed if the account is locked because there have been no logins to the account for a time interval that exceeds the maximum allowed. days is the number of days that the account has been inactive. See the description of the attribute in security(4). is displayed if the account is locked because the number of consecutive authentication failures exceeded the maximum allowed. num is the number of consecutive authentication failures. See the description of the attribute in security(4). is displayed if the account is locked because the account has a null password and is not allowed to have a null password. See the description of the attribute in security(4). is displayed if the account has a time-of-day login restriction. times defines the time periods that the user may login. See the description of the attribute in security(4). Security Restrictions Users invoking this command must have the authorization. See authadm(1M). is not supported for trusted systems. RETURN VALUE
exits with one of the following values: did not find abnormal status found abnormal status invalid usage or user not found EXAMPLES
The following example reports all abnormal status for all local accounts. The following example shows that the account for user is not locked due to too many consecutive authentication failures. FILES
standard password file shadow password file user database SEE ALSO
authadm(1M), passwd(4), security(4), shadow(4), userdb(4). userstat(1M)
All times are GMT -4. The time now is 06:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy