Sponsored Content
The Lounge What is on Your Mind? VBulletin 3.8 to Discourse on Docker Migration Test Take Four Post 303045336 by Neo on Tuesday 17th of March 2020 06:44:19 AM
Old 03-17-2020
Done...

Code:
Updating topic reply counts...
   138032 / 138032 (100.0%)  [10714 items/min]    
Updating first_post_created_at...

Updating user post_count...

Updating user topic_count...

Updating topic users

Updating post timings

Updating featured topic users

Updating featured topics in categories
      123 / 123 (100.0%)  [81 items/min]   n]  
Updating user topic reply counts
   138032 / 138032 (100.0%)  [11368 items/min]  ]  
Resetting topic counters


Done

Backing up now.....

Then will try to migrate "vb thanks" to "discourse likes" with the new script vbulletin_neo5.rb
These 3 Users Gave Thanks to Neo For This Post:
 

7 More Discussions You Might Find Interesting

1. Web Development

Removing VBSEO for vbulletin – Reverting back to vbulletin URLs

Please note, this information was copied from vbseo.com, now showing a database error. This is posted for reference since vbSEO seems to be going out of business: If you ever need to uninstall vBSEO , you can use the following instructions. Make sure you carefully follow each step. Login... (37 Replies)
Discussion started by: Neo
37 Replies

2. Linux

Docker and pipework,ip with other subnet

Recently i found this for give to docker a "personal" ip ip addr del 10.1.1.133/24 dev eth0 ip link add link eth0 dev eth0m type macvlan mode bridge ip link set eth0m up ip addr add 10.1.1.133/24 dev eth0m route add default gw 10.1.1.1On container i did ... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

3. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

4. Shell Programming and Scripting

Problem in extracting yocto SDK for docker

Actually I was facing the following issue while building my Yocto SDK on Docker container sudo docker build --tag="akash/eclipse-che:6.5.0-1" --tag="akash/eclipse-che:latest" /home/akash/dockerimage.yocto.support/ Sending build context to Docker daemon 26.93MB Step 1/5 : FROM eclipse/cpp_gcc ... (3 Replies)
Discussion started by: Akash BHardwaj
3 Replies

5. Docker

Docker learning Phase-I

Hello All, I had recently learnt a bit of Docker(which provides containerization process). Here are some of my learning points from it. Let us start first with very basic question: What is Docker: Docker is a platform for sysadmins and developers to DEPLOY, DEVELOP and RUN applications ... (7 Replies)
Discussion started by: RavinderSingh13
7 Replies

6. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

OK. Like we all do, we learn a lot from tests, test migrations, and so forth. Today, I started from scratch on test migration 2, armed with a lot more knowledge, The main differences are as follows: Installed discourse plugin ruby-bbcode-to-md before starting the install Modified... (30 Replies)
Discussion started by: Neo
30 Replies

7. What is on Your Mind?

Under Consideration: Migrate the Forums to Discourse

Dear All, After being active on the Node-RED forum for the last few weeks, I have been very impressed with Discourse, and my eyes have been opened. https://www.discourse.org/ but not the paid /hosted offering, but using the open distribution: https://github.com/discourse/discourse ... (52 Replies)
Discussion started by: Neo
52 Replies
metadevadm(1M)                                            System Administration Commands                                            metadevadm(1M)

NAME
metadevadm - update metadevice information SYNOPSIS
/usr/sbin/metadevadm [-h] [-n] [ [-l]-r] [-s setname] [-u disk_specifier] [-v] DESCRIPTION
The metadevadm command facilitates the administration of device ID entries in Solaris Volume Manager. Use this command when the pathname stored in the metadevice state database no longer correctly addresses the device or when a disk drive has had its device ID changed. This command requires root privileges. OPTIONS
The following options are supported. -h Provide a help display. -l Specify that metadevadm log to syslog(3C). metadevadm logs to the the DAEMON facility at the ERR level by default. See syslog.conf(4) for additional information on changing logging levels. Use this option anytime. It is most useful in startup scripts and less useful interactively. -n Emulate the effect of a command, without making any changes to the system. -r Recompute the pathname and disk specifier (including slice) associated with all devices in the metadevice state database if the device supports device IDs. If a device does not support device IDs or the device is not available, then no action is taken for that device. Use this option when the disk has been moved or readdressed. This option is run automatically at boot time to detect device ID changes and update the state database. -s setname Specify the name of the disk set on which metadevadm works. This option causes the command to perform its adminis- trative function within the specified disk set. Without this option, the command performs its function on devices in the local disk set. -u disk_specifier Obtain the device ID associated with the disk_specifier (for example, c1t2d0) of a device and update the metadevice state database. If the device ID has not changed this option does nothing. Use this option when a disk drive has had its device ID changed during a firmware upgrade or due to changing the controller of a storage subsystem. -v Execute in verbose mode. This option has no effect when used with -u. Verbose is the default. EXAMPLES
Example 1: Updating Device ID of Disk The following example updates the device c2t3d0: # metadevadm -u c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 The following example is a variation of the preceding, using the full pathname. # metadevadm -u /dev/dsk/c2t3d0 The following example uses the -n option, which means that the command is emulated, but does not take effect. Note that when the -v option is used with -u, -v has no effect (verbose is the default). # metadevadm -u -v -n c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 Example 2: Recomputing Pathnames In the following example, all device names are valid. # metadevadm -r Disk movement detected. Updating device names in SLVM. In the following example, once again device names are valid. # metadevadm -r -v Disk movement detected. Updating device names in SLVM. c0t0d0s0 changed to c0t0d1s0 from device relocation information id12098123lkmklsdjaasdkfjadfjakds In the following example, metadevadm detects an invalid device name. # metadevadm -r Invalid device relocation information detected in SLVM. Please check status of following disk(s): c3t0d0 RETURN VALUES
The following exit values are returned: 0 Command was successful. 1 metadevadm encountered an error condition. 2 An invalid device ID was detected when using the -r option. This is for use in the rc2.d script. See init.d(4). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 13 Sep 2004 metadevadm(1M)
All times are GMT -4. The time now is 05:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy