Sponsored Content
The Lounge What is on Your Mind? Under Consideration: Migrate the Forums to Discourse Post 303045019 by Neo on Wednesday 11th of March 2020 12:54:19 AM
Old 03-11-2020
Regarding this "pm migration errors"

Code:
importing private messages...
skipping pm-2068 `to_user_array` is not properly serialized -- {"bcc"=>"madEG"}
pm-2068 has no target (a:1:{s:3:"bcc";s:5:"madEG";})
     1001 / 32205 (  3.1%)  [4272085 items/min]  skipping pm-2084 `to_user_array` is not properly serialized -- {"bcc"=>"vino"}
pm-2084 has no target (a:1:{s:3:"bcc";s:4:"vino";})
     1002 / 32205 (  3.1%)  [3945003 items/min]  skipping pm-2099 `to_user_array` is not properly serialized -- {"bcc"=>"jamcalicut"}
pm-2099 has no target (a:1:{s:3:"bcc";s:10:"jamcalicut";})
     1003 / 32205 (  3.1%)  [3655451 items/min]  skipping pm-2100 `to_user_array` is not properly serialized -- {"bcc"=>"arunkumar_mca"}
pm-2100 has no target (a:1:{s:3:"bcc";s:13:"arunkumar_mca";})
     1004 / 32205 (  3.1%)  [3458157 items/min]  skipping pm-2106 `to_user_array` is not properly serialized -- {"bcc"=>"thanusha"}
pm-2106 has no target (a:1:{s:3:"bcc";s:8:"thanusha";})
     1005 / 32205 (  3.1%)  [3408788 items/min]  skipping pm-2108 `to_user_array` is not properly serialized -- {"bcc"=>"Danielillo300"}

  blah, blah, blah

I think I'll look at the code and just comment this out, if necessary, as there is no compelling reason to spend a lot of time on migrating pms "perfectly", I think,.

EDIT: On second thought, "skipping these handful of pms" is not going to harm the migration, so I think I will 'let this be" and move on.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to migrate ?

Currently, I am planning a migration between machine which under True64UNIX. The new machine will run with higher version O/S. My question is, is there any solution on migrating one machine to another which with different O/S version? My goal is keeping minimum impact to the users. Excuse my... (1 Reply)
Discussion started by: coolmans
1 Replies

2. UNIX for Dummies Questions & Answers

Pipe not taken into consideration

I'm trying to see every file which my group (staff) has in a certain directory, recursively. The pipe ls -l -R | grep staff is not working exactly as I want, as for every directory to which my user does not have access, a line like: ls: ./directory/lost+found: The file access permissions do not... (5 Replies)
Discussion started by: panchopp
5 Replies

3. Solaris

Migrate oracle solaris 5.8 5.9

If I have an oracle 9 database environment on a san running solaris 5.8 as the os. Can I plug the san into a Solaris 5.9 environment and have the database work ? - as long as binaries are on the san (1 Reply)
Discussion started by: tim-carroll@com
1 Replies

4. Solaris

Can you migrate UFS to ZFS ?

I have some UFS volumes (non root), that I would like to change into ZFS volumes. Is this possible ? I think the only method is to create a new zfs volume and copy the data accoss, this would take a long time for us. Is there a quicker way ? Regards (5 Replies)
Discussion started by: wjones
5 Replies

5. Solaris

Migrate from MPXIO to Powerpath

Here is the issue: I am building a database server using Solaris 10x86 U8. The system is jumpstarted with mpxio enabled and booting from the san. We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies

6. Linux

Mysql Migrate

Hi , I would like to (MYSQL) migrate the all the data from solari's to linux box. I have checked whether mysql is installed or not. rpm -qa | grep -i mysql I confirmed !!!! I want to know the following points. 1) How can get to know what are mysql data files and location as well.... (4 Replies)
Discussion started by: Mani_apr08
4 Replies

7. BSD

Migrate a Hard Disk

hi Has anyone already tried to migrate a hard disk with FreeBSD using recoverdisk? (1 Reply)
Discussion started by: ccc
1 Replies

8. Shell Programming and Scripting

Migrate from FTP to SFTP

Hi,I am using following code for FTP in shell script file and it is working.Now I want to migrate from FTP to SFTP.What code changes/steps I have to perform for SFTP ? ftp -in <<FIN open $SAP_UP_SERVER user $SAP_UP_USER $SAP_UP_PASSWORD asc put... (7 Replies)
Discussion started by: Nitin Varshneya
7 Replies
bcc(1)							      General Commands Manual							    bcc(1)

NAME
bcc - Bruce's C compiler SYNOPSIS
bcc [-03EGNOPSVcegvwxW] [-Aas_option] [-Bexecutable_prefix] [-Ddefine] [-Uundef] [-Mc_mode] [-o outfile] [-ansi] [-Ccc1_option] [-Iinclude_dir] [-Lld_option] [-Ttmpdir] [-Qc386_option] [-ttext_segno] [ld_options] [infiles] DESCRIPTION
Bcc is a simple C compiler that produces 8086 assembler, in addition compiler compile time options allow 80386 or 6809 versions. The compiler understands traditional K&R C with just the restriction that bit fields are mapped to one of the other integer types. The default operation is to produce an 8086 executable called a.out from the source file. OPTIONS
-ansi Pass the C source through unprotoize after preprocessing and before code generation. This will allow some ansi C to be compiled but it is definitly NOT a true ansi-C compiler. -0 8086 target (works on 80386 host, but not 6809) -3 80386 target (may work on 8086 host, but not 6809) -A pass remainder of option to assembler (e.g. -A-l -Alistfile for a listing) -B prefix for executable search path (as usual; the search order is all paths specified using -B, in order, then the path given in the environment variable BCC_EXEC_PREFIX if that is set, then the compiled-in defaults (something like /usr/lib/bcc/ followed by /usr/bin/) -C pass remainder of option to bcc-cc1, see code generation options. -D preprocessor define -E produce preprocessor output to standard out. -G produce GCC objects (only useful for i386 code) -Ixyz include search 'xyz' path -I don't add default include to search list -Lxyz add directory name 'xyz' to the head of the list of library directories searched -L don't add default library to search list -Md alters the arguments for all passes to produce MSDOS executable COM files. These are small model executables, use -i to get tiny model. -Mf sets bcc to pass the -c and -f arguments to the code generator for smaller faster code. Note this code is not compatible with the standard calling conventions so a different version of the C library is linked too. -Mc sets bcc to pass the -c argument to the code generator for smaller faster code. Note the standard libc is normally transparent to this, but there are exceptions. -Ms alters the arguments for all passes and selects C-library to produce standalone Linux-86 executables -Ml switches to i386-Linux code generator and library. This configuration accepts the -z flag to generate QMAGIC a.out files instead of the normal OMAGIC. -N makes the linker produce a native a.out file (Linux OMAGIC) if combined with -3 the executable will run under Linux-i386. -O optimize, call copt(1) to optimize 8086 code. Specifiers to choose which rules copt should use can be appended to the -O and the option can be repeated. -P produce preprocessor output with no line numbers to standard output. -Q pass full option to c386 (Only for c386 version) -S produce assembler file -T temporary directory (overrides previous value and default; default is from the environment variable TMPDIR if that is set, otherwise /tmp) -U preprocessor undefine -V print names of files being compiled -X pass remainder of option to linker (e.g. -X-Ofile is passed to the linker as -Ofile) -c produce object file -e run the preprocess pass separately. This takes less memory, and may help or harm by giving more traditional semantics like token pasting with /**/. -f error (float emulation not supported) -g produce debugging info (does nothing) -o output file name follows (assembler, object or executable) (as usual) -p error (profiling not supported) -t1 pass to the assembler to renumber the text segment for multi-segment programs. -v print names and args of subprocesses being run. Two or more -v's print names of files being unlinked. Three or more -v's print names of paths being searched. -w Supress any warning diagnostics. -W Turn on assembler warning messages. -x don't include crt0.o in the link. -i don't pass -i to the linker so that it will create an impure executable. Other options are passed to the linker, in particular -lx, -M, -m, -s, -H. CODE GENERATOR OPTIONS
These are all options that the code generator pass bcc-cc1 understands, only some will be useful for the -C option of bcc. The code generator is normally used as a combined C preprocessor and generator but the -e and -ansi options of bcc split the operation. -0 8086 target (works even on 80386 host, not on 6809) -3 80386 target (may work even on 8086 host, not on 6809) -D define (as usual) -E produce preprocessor output (as usual) -I include search path (as usual) -P produce preprocessor output with no line numbers (as usual) -c produce code with caller saving regs before function calls -d print debugging information in assembly output -f produce code with 1st argument passed in a register (AX, EAX or X) -l produce code for 2 3 1 0 long byte order (only works in 16-bit code), a special library of compiler helper functions is needed for this mode. -o assembler output file name follows -p produce (almost) position-independent code (only for the 6809) -t print source code in assembly output -w print what cc1 thinks is the location counter in assembly output All the options except -D, -I and -o may be turned off by following the option letter by a '-'. Options are processed left to right so the last setting has precedence. PREPROCESSOR DEFINES
The preprocessor has a number of manifest constants. __BCC__ 1 The compiler identifier, normally used to avoid compiler limitations. __FILE__ stringized name of current input file __LINE__ current line number __MSDOS__ 1 compiler is configured for generating MSDOS executable COM files. __STANDALONE__ 1 compiler is configured for generating standalone executables. __AS386_16__ 1 compiler is generating 16 bit 8086 assembler and the #asm keyword is available for including 8086 code. __AS386_32__ 1 compiler is generating 32 bit 80386 assembler and the #asm keyword is available for including 80386 code. __CALLER_SAVES__ 1 compiler calling conventions are altered so the calling function must save the SI and DI registers if they are in use (ESI and EDI on the 80386) __FIRST_ARG_IN_AX__ 1 compiler calling conventions are altered so the calling function is passing the first argument to the function in the AX (or EAX ) register. __LONG_BIG_ENDIAN__ 1 alters the word order of code generated by the 8086 compiler. These defines only occur in the 6809 version of the compiler. __AS09__ 1 compiler is generating 6809 code __FIRST_ARG_IN_X__ 1 the first argument to functions is passed in the X register. __POS_INDEPENDENT__ 1 the code generated is (almost) position independent. ENVIRONMENT
BCC_EXEC_PREFIX default directory to seach for compiler passes TMPDIR directory to place temporary files (default /tmp) DIRECTORIES
All the include, library and compiler components are stored under the /usr/bcc directory under Linux-i386, this is laid out the same as a /usr filesystem and if bcc is to be the primary compiler on a system it should be moved there. The configuration for this is in the bcc.c source file only, all other executables are independent of location. The library installation also creates the file /usr/lib/liberror.txt, this path is hardcoded into the C library. The bcc executable itself, as86 and ld86 are in /usr/bin. SEE ALSO
as86(1), ld86(1), elksemu(1) BUGS
The bcc.c compiler driver source is very untidy. The linker, ld86, produces a broken a.out object file if given one input and the -r option this is so it is compatible with pre-dev86 versions. Nov, 1997 bcc(1)
All times are GMT -4. The time now is 04:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy