04-28-2020
Yes, the thread title in the migrated post is different because there is no migration script running against titles.
That's not a big deal, it's a total outlier.
We are not processing "thread titles" in the migration (on migration scripts do) because the migration scripts are not designed to process any titles at all.
All processing is for the posts only.
Let's don't go chasing down outlier rabbit holes where we are not even concerned about.
It takes less time to edit an outlier like that than to discuss it, LOL.
Obviously, is a thread title has a char which is not encoded properly, then it will have issues when migrated. That is like some 0.00001 kinda outlier.
It's good you found it so we can edit it later; but it's nothing to be concerned about.
So, to be clear... the migration script does not do any processing on titles. Titles are expected to be written in "basic normal charsets" and when they are not, it is quite the outlier case.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am writing a bash shell menu and would like to get a char immediately after a key is pressed. This script does not work but should give you an idea of what I am trying to do....
Thanks for the help
#! /bin/bash
ANSWER=""
echo -en "Choose item...\n"
until
do
$ANSWER = $STDIN
... (2 Replies)
Discussion started by: jwzumwalt
2 Replies
2. Shell Programming and Scripting
I created one file on windows system and is visible as :
TestTable,INSERT,večilnin1ईगल受害者是第,2010-02-02 10:10:10.612447,137277,ईगल受害者是第večilnin!@#$%^&*()_+=-{}]
But when send this file to unix system, the file is visible as :
TestTable,INSERT,žvečilnin1ई-ल -害...是第,2010-02-02 ... (4 Replies)
Discussion started by: Shaishav Shah
4 Replies
3. Solaris
Hi All,
We need to move Physical Solaris 10 system to Virtual Solaris 10(p2v). Both the servers having Solaris 10(Generic_147440-25) means physical server which we are going to move is having Solaris 10 and this physical server will be converted as a virtualserver on another physical server... (9 Replies)
Discussion started by: sb200
9 Replies
4. UNIX for Dummies Questions & Answers
Hello All,
PC: CuBox-i (*i.MX6) Mini-PC
OS: openSUSE 13.1 (Bottle) (armv7hl)
Kernel: 3.14.14-cubox-i
# uname -a
Linux CuBox-HQ 3.14.14-cubox-i #1 SMP Sat Sep 13 03:48:24 UTC 2014 armv7l armv7l armv7l GNU/LinuxSo I've been having this random issue happen on this PC where a few strange... (12 Replies)
Discussion started by: mrm5102
12 Replies
5. AIX
Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this :
lslpp -l | grep EMC
... (7 Replies)
Discussion started by: JME2015
7 Replies
6. Shell Programming and Scripting
Greetings Experts,
We are migrating from AIX to RHEL Linux. I have created a script to verify and report the NULLs and SPACEs in the key columns and duplicates on key combination of "|" delimited set of big files. Following is the code that was successfully running in AIX.
awk -F "|" 'BEGIN {... (5 Replies)
Discussion started by: chill3chee
5 Replies
7. Solaris
Hi all!!
Im using command file -i myfile.xml to validate XML file encoding, but it is just saying regular file . Im expecting / looking an output as UTF8 or ANSI / ASCII
Is there command to display the files encoding?
Thank you! (2 Replies)
Discussion started by: mrreds
2 Replies
LEARN ABOUT DEBIAN
smokeping_probes_nfsping
Smokeping_probes_NFSping(3) SmokePing Smokeping_probes_NFSping(3)
NAME
Smokeping::probes::NFSping - NFSping Probe for SmokePing
SYNOPSIS
*** Probes ***
+NFSping
binary = /usr/local/bin/nfsping # mandatory
blazemode = true
hostinterval = 1.5
mininterval = 0.001
offset = 50%
pings = 20
step = 300
timeout = 1.5
# [...]
*** Targets ***
probe = NFSping # if this should be the default probe
# [...]
+ mytarget
# probe = NFSping # if the default probe is something else
host = my.host
DESCRIPTION
Integrates NFSping as a probe into smokeping. The variable binary must point to your copy of the NFSping program.
NFSping can be downloaded from:
<https://github.com/mprovost/NFSping>
In blazemode, NFSping sends one more ping than requested, and discards the first RTT value returned as it's likely to be an outlier.
VARIABLES
Supported probe-specific variables:
binary
The location of your nfsping binary.
Example value: /usr/local/bin/nfsping
This setting is mandatory.
blazemode
Send an extra ping and then discard the first answer since the first is bound to be an outlier.
Example value: true
hostinterval
The nfsping "-p" parameter, but in (possibly fractional) seconds rather than milliseconds, for consistency with other Smokeping probes.
This parameter sets the time that nfsping waits between successive packets to an individual target.
Example value: 1.5
mininterval
The nfsping "-i" parameter, but in (probably fractional) seconds rather than milliseconds, for consistency with other Smokeping probes.
This is the interval between pings to successive targets.
Example value: 0.001
Default value: 0.01
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
pings
How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the
number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have
to delete the old RRD files or somehow convert them.
Example value: 20
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
timeout
The nfsping "-t" parameter, but in (possibly fractional) seconds rather than milliseconds, for consistency with other Smokeping probes.
Example value: 1.5
AUTHORS
Tobias Oetiker <tobi@oetiker.ch> Matt Provost <mprovost@termcap.net>
2.6.8 2013-03-17 Smokeping_probes_NFSping(3)