Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Bits - The Unix and Linux Forums (Experimental) Virtual Currency Post 302764177 by Neo on Thursday 31st of January 2013 05:04:31 AM
Old 01-31-2013
Hi Praveen,

For the foreseeable future, we are going to hold the number of bits constant and we are going to reclaim bits when members are inactive. We are not going to "inflate" bits so inactive members can keep them in their account.

And, based on the economic numbers, there is no reason to "inflate" the economy to account for inactive users. I can assure you, active members who do not have their bits reclaimed after inactivity (because they are active) are not advocating a change in the system or inflating bits Smilie And, as mentioned, the "economic numbers" on the banking page speak for themselves - there is no reason to create a policy of bit inflation to account for inactive users; as this decreases the "forum value" of "activity bits" for active members of the community.

We are going to keep things as they are for the foreseeable future; and we reserve the right to change the time period of inactivity to 5 months, 3 months, one month; based on what we see as system admins. Based on what we have seen over the past year, 6 months is just about the right "reclaim period" and this will remain our policy as long as it works well for the system.

Thank you for your comments.
 

6 More Discussions You Might Find Interesting

1. What is on Your Mind?

The UNIX and Linux Forums Twitter Channel

In case you did not know about this, and are a twitter user, here is the link to the forum twitter channel: http://twitter.com/unixlinux We currently have 406 followers...... (0 Replies)
Discussion started by: Neo
0 Replies

2. What is on Your Mind?

Experimental New UNIX / Linux Project Board (See Toolbar)

We are experimenting with a new project board to help forum members make extra cash; because we have some very talented members, why not make some extra cash working from your computer. See toolbar at bottom of page. Any ideas or comments? ... (0 Replies)
Discussion started by: Neo
0 Replies

3. Post Here to Contact Site Administrators and Moderators

How to Advertise on The Unix and Linux Forums

We added a new way to advertise (to guests and non-registered users) directly on the forums: Advertise directly with The UNIX and Linux Forums https://www.unix.com/members/1-albums112-picture605.png Companies and individuals can buy display ads directly and submit their display ads... (0 Replies)
Discussion started by: Neo
0 Replies

4. How to Post in the The UNIX and Linux Forums

How to Navigate in UNIX & Linux Forums..?

Hi , i am a new user to this forum can anyone please help me in navigation for this forum. also when i am trying to open any thread i am getting below error. Bad Request Your browser sent a request that this server could not understand.] Thanks. (1 Reply)
Discussion started by: nkchand
1 Replies

5. Post Here to Contact Site Administrators and Moderators

VIP Membership - The UNIX and Linux Forums - Get Your UNIX.COM Email Address Here

We work hard to make The UNIX and Linux Forums one of the best UNIX and Linux knowledge sources on the net. The site is certainly one of the top UNIX and Linux Q&A sites on the web. In order to provide certain members the best quality account services, you can now get some great extra features by... (2 Replies)
Discussion started by: Neo
2 Replies

6. What is on Your Mind?

YouTube: Forum Moderation @UNIX.com | The UNIX and Linux Forums

Forum Moderation @UNIX.com | The UNIX and Linux Forums https://youtu.be/WGwgibE4Rq0 Also note: In the video I mentioned removing legacy menu items in the ModCP which are unused. I have already "CSS'ed out" the unused menu items: ... (0 Replies)
Discussion started by: Neo
0 Replies
chage(1)						      General Commands Manual							  chage(1)

NAME
chage - change user password expiry information SYNOPSIS
chage [-D binddn] [-P path] [-m mindays] [-M maxdays] [-d lastday] [-I inactive] [-E expiredate] [-W warndays] user chage -l [user] DESCRIPTION
chage is used to list and change the password expiry information of a user. It allows the system administrator to change the number of days between allowed and required password changes and the date of the last password change. It allows also to define when an account will expire. The chage command is restricted to the system administrator, except for the -l option, which may be used by an user to determine when his password or account is due to expire. If no option is given, chage operates in an interactive mode, prompting the user with the current values for all of the fields. Enter the new value to change the field, or leave the line blank to use the current value. If the users exists in the local passwd file, but not in the local shadow file, chage will create a new entry in the shadow file. OPTIONS
-D, --binddn binddn Use the Distinguished Name binddn to bind to the LDAP directory. The user will be prompted for a password for simple authentica- tion. -P, --path path The passwd and shadow files are located below the specified directory path. chage will use this files, not /etc/passwd and /etc/shadow. This is useful for example on NIS master servers, where you do not want to give all users in the NIS database auto- matic access to your NIS server and the NIS map is build from special files. -l, --list This option will list the password expiry information in a human readable format. The user will see the date when he changed the password the last time, when the password will be expire, when the password will be locked and when the account will expire. -m, --mindays mindays With this option the minimum number of days between password changes is changed. A value of zero for this field indicates that the user may change her password at any time. Else the user will not be permitted to change the password until min days have elapsed. -M, --maxdays maxdays With this option the maximum number of days during which a password is valid is changed. When maxdays plus lastday is less than the current day, the user will be required to change his password before being able to use the account. -d, --lastday lastday With this option the date when the password was last changed can be set to another value. lastday has to be specified as number of days since January 1st, 1970. The date may also be expressed in the format YYYY-MM-DD. If supported by the system, a value of zero forces the user to change the password at next login. -E, --expiredate expiredate With this option the date when the account will be expired can be changed. expiredate has to be specified as number of days since January 1st, 1970. The date may also be expressed in the format YYYY-MM-DD. -I, --inactive inactive This option is used to set the number of days of inactivity after a password has expired before the account is locked. A user whose account is locked must contact the system administrator before being able to use the account again. A value of -1 disables this feature. -W, --warndays warndays With this option the number of days of warning before a password change is required can be changed. This option is the number of days prior to the password expiring that a user will be warned the password is about to expire. FILES
passwd - user account information shadow - shadow user account information SEE ALSO
passwd(1), passwd(5) AUTHOR
Thorsten Kukuk <kukuk@suse.de> pwdutils November 2005 chage(1)
All times are GMT -4. The time now is 04:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy