Future New Underground Membership Criteria Post: 303029013

Sponsored Content

The Lounge What is on Your Mind? Future New Underground Membership Criteria Post 303029013 by Don Cragun on Saturday 19th of January 2019 04:20:25 PM

01-19-2019

Registered User

Quote:

Originally Posted by Neo

OK... until we get some better ideas, the system will run this cron once a day:

Code:

<?php
$promote_ug = "update  user set usergroupid =13, usertitle='Forum Advisor', customtitle=1  where posts > 100 AND lastactivity > (UNIX_TIMESTAMP() - (3600*24*60)) and usergroupid = 2 and post_thanks_thanked_times > 25";

$status_up = $vbulletin->db->query_write($promote_ug); 

$demote_ug = "update user set usergroupid = 2, usertitle='Registered User', customtitle=1 WHERE lastactivity <  (UNIX_TIMESTAMP() - (3600*24*60)) and usergroupid = 13"; 

$status_down = $vbulletin->db->query_write($demote_ug);

Looking forward to some great ideas on changing this criteria or adding new badges / user groups.

Am I reading the above code correctly to believe that if someone has paid 400000 bits to get a custom title, this code will automatically discard that custom title if that user is promoted to or demoted to the underground? Shouldn't custom titles that have been paid for remain with that user (getting only color changes in the title to indicate changes in level) unless that user asked to have the custom title removed?

One of the (private) notes that is about to be or recently was deleted said that a user wasn't going to be asked to become a moderator because it could put him in an awkward position at his job (due to a possible conflict of interest). If that was a valid concern then, should there ever be a promotion without asking the user if (s)he wants that honor first?

Don Cragun

View Public Profile for Don Cragun

Find all posts by Don Cragun

3 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Membership

what is the meaning of the types of membership and when am i a full member:confused: :confused: :confused:

2. Solaris

Group membership limit

On Solaris, a user is limited to being a member of a maximum of 16 groups. Could someone tell me where this limit comes from, i.e. is it NIS, or Solaris, or NFS that is imposing this limit? What is the work-around to remove this limitation?

3. Post Here to Contact Site Administrators and Moderators

monthly membership??

Hi, Do we have monthly membership (VIP) in our forum? if not, do we have any plans for it? Regards,

LEARN ABOUT XFREE86

queuedefs

queuedefs(4)							   File Formats 						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q	The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
		at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob	The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
		njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice	The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
		queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All	other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs	       queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10							    1 Mar 1994							      queuedefs(4)