Migrating "vb thanks" to "discourse likes" (have not found a reliable simple solution to this yet except, of course pattern matching in the postgres DB is always an option, but this will be painfully slow).
Not sure how all the various kinds of attachments will migrate, since the vb site has many different legacy attachment methods, so we may not migrate over most of them.
Will not migrate the following:
PMs (no reason to migrate these).
Passwords (the hash functions are different so better to reset using "lost password", which works fine and all password will follow the discourse rules),
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT OSF1
numa_scheduling_groups
numa_scheduling_groups(4) Kernel Interfaces Manual numa_scheduling_groups(4)NAME
numa_scheduling_groups - Compaq Tru64 UNIX NUMA Scheduling Groups description (libnuma library)
DESCRIPTION
Normally, the kernel scheduler attempts to distribute the workload evenly over the entire machine. When the system resources are evenly
utilized, the machine is considered to be balanced. When balancing the workload, the scheduler operates in a context-free manner; that is,
processes may be distributed to various CPUs, or other resources, without regard to their function or relationship to one another. In cer-
tain cases, a user may wish to bundle a group of processes together so that they have equal access to the same system resources. For
instance, cooperating processes that share the same physical memory may perform better if all of these processes execute on CPUs that are
local to that memory.
NUMA Scheduling Groups (NSG) cause the scheduler load-balancing system to treat all members of an NSG as a unit. If one process belonging
to an NSG moves from one Resource Affinity Domain (RAD) to another, all other members of the NSG have to move with it.
NSGs and their members have the following characteristics: The resource domain of the first process joining an NSG provides the initial
resource domain location for that NSG, called the NSG home RAD. All other processes joining the NSG (through the nsg_attach_pid() func-
tion) will be migrated to the NSG home RAD. If the joining process is not allowed to migrate, the nsg_attach_pid() function will fail. To
support load balancing, an NSG is allowed to migrate to any RAD on the system if none of its members is bound to a specific resource (such
as another RAD, CPU, and so on). An NSG member is allowed to attach to or bind to a resource only if no other members are bound to differ-
ent resources. The entire NSG will migrate to the RAD containing the resource at the time it was successfully bound. If one NSG member is
bound to a resource, all other members of that NSG are also bound to the RAD containing that resource, because the NSG and, therefore its
members, is no longer allowed to migrate.
SEE ALSO
Commands: runon(1)
Functions: bind_to_cpu(3), nsg_attach_pid(3), nsg_detach_pid(3), nsg_destroy(3), nsg_get(3), nsg_get_pids(3), nsg_init(3), nsg_set(3),
numa_intro(3), rad_attach_pid(3), rad_bind_pid(3), rad_detach_pid(3)numa_scheduling_groups(4)