04-26-2020
Update1:
Update2:
- Added two columns to the vb3 post table, discourse_topic_id and the discourse_post_id
- Added one column to the vb3 thread table, discourse_topic_id
- Added Ruby code to the migration script preprocessing control which inserts the discourse_topic_id and the discourse_post_id of the migrated posts back into the mysql dump for the vb3 post and thread tables.
After migration will update the original vb3 post and thread table so we have the mappings to the discourse_post_id and discourse_thread_id, which we will use for a number of redirections and links in the future.
This means, for example, when someone clicks on an old thread in the legacy vb3 forum to reply, we can send them to the new thread to reply.
Cheers.
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view.
I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
Discussion started by: arvindcgi
4 Replies
2. HP-UX
All,
We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers.
HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800)
HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Discussion started by: helper
2 Replies
3. Programming
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies
4. What is on Your Mind?
First a bit of history ....
A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
Discussion started by: Neo
1 Replies
5. What is on Your Mind?
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
6. What is on Your Mind?
Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily:
Insuring ruby-bbcode-to-markdown is enabled.
Removing line breaks from ICODE to markdown in migration script.
Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies
LEARN ABOUT FREEBSD
gsignal
PSIGNAL(9) BSD Kernel Developer's Manual PSIGNAL(9)
NAME
psignal, pgsignal, gsignal, tdsignal -- post signal to a thread, process, or process group
SYNOPSIS
#include <sys/types.h>
#include <sys/signalvar.h>
void
psignal(struct proc *p, int signum);
void
pgsignal(struct pgrp *pgrp, int signum, int checkctty);
void
gsignal(int pgid, int signum);
void
tdsignal(struct thread *td, int signum);
DESCRIPTION
These functions post a signal to a thread or one or more processes. The argument signum common to all three functions should be in the range
[1-NSIG].
The psignal() function posts signal number signum to the process represented by the process structure p. With a few exceptions noted below,
the target process signal disposition is updated and is marked as runnable, so further handling of the signal is done in the context of the
target process after a context switch. Note that psignal() does not by itself cause a context switch to happen.
The target process is not marked as runnable in the following cases:
o The target process is sleeping uninterruptibly. The signal will be noticed when the process returns from the system call or trap.
o The target process is currently ignoring the signal.
o If a stop signal is sent to a sleeping process that takes the default action (see sigaction(2)), the process is stopped without
awakening it.
o SIGCONT restarts a stopped process (or puts them back to sleep) regardless of the signal action (e.g., blocked or ignored).
If the target process is being traced psignal() behaves as if the target process were taking the default action for signum. This allows the
tracing process to be notified of the signal.
The pgsignal() function posts signal number signum to each member of the process group described by pgrp. If checkctty is non-zero, the sig-
nal will be posted only to processes that have a controlling terminal. pgsignal() is implemented by walking along the process list headed by
the field pg_members of the process group structure pointed at by pgrp and calling psignal() as appropriate. If pgrp is NULL no action is
taken.
The gsignal() function posts signal number signum to each member of the process group identified by the group id pgid. gsignal() first finds
the group structure associated with pgid, then invokes pgsignal() with the argument checkctty set to zero. If pgid is zero no action is
taken.
The tdsignal() function posts signal number signum to the thread represented by the thread structure td.
SEE ALSO
sigaction(2), signal(9), tsleep(9)
BSD
October 8, 2011 BSD