Sponsored Content
The Lounge What is on Your Mind? Current Array of Badges (Beta 1) Post 303028433 by Neo on Tuesday 8th of January 2019 06:14:41 AM
Old 01-08-2019
Also, I want to thank everyone for their patience as we continue to develop our new badging system.

It's going to be great and these things take time; so that you for your patience during this growth and transition phase.

When the badging system is developed it will be easier for moderators to moderate the forums and all moderation will be completely transparent to all members. In addition, the badging system will help all members understand their progress, activity and participation in the forums.

Thank you again for your patience as I code this new system for the benefit of everyone.
These 4 Users Gave Thanks to Neo For This Post:
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to compare current record,with next and previous record in awk without using array?

Hi! all can any one tell me how to compare current record of column with next and previous record in awk without using array my case is like this input.txt 0 32 1 26 2 27 3 34 4 26 5 25 6 24 9 23 0 32 1 28 2 15 3 26 4 24 (7 Replies)
Discussion started by: Dona Clara
7 Replies

2. Hardware

Stack Overflow Questions Tags Users Badges Unanswered Ask Question Ask for the explanation of types

I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks! RAM on disk drive controllers 1 firmware 2 speed matching buffer 3 prefetching buffer 4 cache (1 Reply)
Discussion started by: 915086731
1 Replies

3. 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

4. What is on Your Mind?

Four More UNIX.COM Achievement Award Badges to Award

Happy New Year! There are currently four UNIX.COM achievement awards up for grabs, as the say. Here they are, in no particular order: The Order of the Raven The Order of the Hippo The Order of the Spider The Order of the Dragon Don't ask me what they mean, or who who will get those... (0 Replies)
Discussion started by: Neo
0 Replies

5. Web Development

Current New Badge Alert Script (Beta 1)

Here is the JS I wrote and am now testing live for alerting a member when they have received a new badge (seems to be working OK so far, still testing live): var badgeChange = readCookie("badgestatechange"); $(function() { if (badgeChange == "1") { if (vbuserId > 0) { var... (0 Replies)
Discussion started by: Neo
0 Replies

6. What is on Your Mind?

Patreon Badges Now Available as BBCODE at UNIX.COM

Dear All, We have a lot of amazing moderators and other very talented unix.com members who provide tireless top quality free technical support assistance to others. As a service to those long term unix.com members, I am making a new Patreon BBCODE badge available which can be posted in forum... (8 Replies)
Discussion started by: Neo
8 Replies

7. What is on Your Mind?

My Badges Page - A Major UserCP Update (v0.661):

Another major upgrade on the new UserCP today. I have created the "My Badges" page in the new control panel, and it's looking very cool :) If you have visited the new UserCP recently, you will more-than-likely need to close your browser (completely) and then restart it to clear out the old... (2 Replies)
Discussion started by: Neo
2 Replies
versw(8)						      System Manager's Manual							  versw(8)

NAME
versw - Manages the transition from the active version of the operating system to a new version SYNOPSIS
/usr/sbin/versw [option...] OPTIONS
Checks whether a version switch is pending. The versw utility returns a 1 if a version switch is pending (the active and new versions dif- fer), a 0 if a version switch is not pending (the active and new versions are the same). Sets the versw_transition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 0 (zero). Prints the old (previously active), active, and new version IDs, the version transition state, and the version switch state. If a version switch is in progress, the version switch state is the member ID of the cluster member running the versw utility plus 100. Otherwise, the version switch state is 0. Unconditionally sets the active version ID to the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the member's running kernel. Specifies a directory path to an alternative /etc/sysconfigtab file. By default, the member-specific /etc/sysconfigtab file is used. Sets the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the running kernel. The installation of the Tru64 UNIX operating system and the cluster software automatically sets these values. Sets the versw_tran- sition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 1. When run with the -switch option, the versw utility automatically sets this attribute. Attempts to set the active version ID to the new version ID on a standalone system or on all currently active cluster members. When you install Tru64 UNIX on a standalone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. When you complete a cluster rolling upgrade, by issuing a clu_upgrade -switch, clu_upgrade automatically issues the versw -switch command to set the active and new versions consistently on all cluster members. Checks the return value from the versw() function. See versw(3) for a description of this function. DESCRIPTION
The versw utility manages the transition from the active version of the operating system to a new version. You must be root to use this utility. The active and new operating system versions are recorded in the act_vers and new_vers attributes, respectively, in the generic kernel sub- system of the /etc/sysconfigtab file (or each member's /etc/sysconfigtab file in a cluster). When you install a new version of the Tru64 UNIX operating system or cluster software, the installation procedure automatically issues the versw -setnew command to establish the new version ID in the /etc/sysconfigtab file and in the running kernel. At installation time, the new version ID must always be higher than the active version ID. When installation completes on a standalone system, the active and new versions will be identical. When you install Tru64 UNIX on a stand- alone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. During a rolling upgrade of a cluster, the active and new versions will not be the same on each cluster member until the rolling upgrade completes. When you conclude the rolling upgrade, by issuing the clu_upgrade -switch command, clu_upgrade automatically issues the versw -switch command to set the active and new versions equal on all cluster members. After all cluster members have been rebooted with the new active version, all features of the new operating system and cluster software are enabled across all cluster members. When called by the clu_upgrade -switch command in a cluster, the versw utility performs the following operations: Compares the active and new version IDs in each member's running kernel. If new versions of the operating system and cluster software have been installed, the new version ID will be higher than the active version ID. If the IDs are identical or the new version ID is less than that of the active ver- sion, the utility issues a warning and exits. Checks that each member's /etc/sysconfigtab file is accessible. If not, the utility issues a warning and exits. Checks that all members have booted with the new version. If not, the utility issues a warning and you must either reboot the members or run versw -forcesw to continue. Use the clu_get_info command to determine which systems are running at or below their installed version. Checks for blocking conditions. If any exist, the the versw utility prints an error message and exits. If the new soft- ware has introduced a change or enhancement that is incompatible with the active version, the component sets up a condition that blocks the rolling upgrade. Such incompatibilities usually involve changes to configuration files, on-disk structures, or local or remote interface protocols. Operating system components establish a blocking condition by placing files in the /var/adm/versw directory. These text files provide instructions for manually restoring compatibility between installed and new versions: for instance, by editing a configuration file or running a data conversion script. You must follow the directions in these files to proceed with the upgrade. Moving these files to another directory removes the blocking condition. Determines whether all running members are capable of the switch this member is propos- ing. If not, it displays an error and exits. Sets the versw_transition attribute in the generic kernel subsystem in each member's /etc/sysconfigtab file (and in each member's running kernel) to 1. Requests that the connection manager stop new members from joining the cluster until the completion of the version switch. Sets the active version to the new version in the generic kernel subsystem of each cluster member's /etc/sysconfigtab file. Note that, if a member goes down during this stage, the versw utility exits with an error message. All running members clear their versw_transition attributes and restore their /etc/sysconfigtab copies. Sets the versw_transition attribute in the generic kernel subsubsystem of each member's /etc/sysconfigtab file to 0. Sends a clusterwide clu.versw EVM event to sig- nify that the version switch was successful. EXAMPLE
The following example shows how a script might use the versw -check command to enable new features on a cluster member that has completed a version switch: #!/usr/bin/ksh -p # Script example usage of versw command switch # if versw -check ; then echo "Enable new version features" else echo "Disable new version features" fi The following command shows the output of the versw -dump command on a cluster that has completed a roll: # versw -dump Old version = ( 0 , 0 ) Active version = ( 14000800009a1700 , 3b88 ) New version = ( 14000800009a1700 , 3b88 ) Version transition state = 0 Version switch state = 0 FILES
Specifies the command path. Configurable subsystem definition database file, as specified to the -mount option of the versw utility. By default, the /etc/sysconfigtab file is used. In a cluster, /etc/sysconfigtab is a context-dependent symbolic link (CDSL) that references the sysconfigtab file for a member. Rolling upgrade blocking conditions directory. SEE ALSO
Functions: versw(3), clu_is_member(3), clu_get_info(3) versw(8)
All times are GMT -4. The time now is 04:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy