Sponsored Content
The Lounge What is on Your Mind? Under Consideration: Migrate the Forums to Discourse Post 303044923 by Neo on Monday 9th of March 2020 07:08:15 AM
Old 03-09-2020
Currently chugging along, importing users sans avatars and passwords.

Code:
root@localhost-app:/var/www/discourse# su discourse -c 'bundle exec ruby script/import_scripts/vbulletin.rb'
discourse:@localhost wants vb5
Loading existing groups...
Loading existing users...
Loading existing categories...
Loading existing posts...
Loading existing topics...

importing groups...
       20 / 20 (100.0%)  [1918542 items/min]  
importing users
   106664 / 138120 ( 77.2%)  [9832 items/min]

Just upgraded the test bed slice from 2GB to 8GB and increase RAM and quadrupled the CPU power and disk space (was getting tight)..... Hopefully it will chug along every faster.

Code:
8 GB	4 Cores	160 GB SSD	5 TB	40 Gbps	5000 Mbps

This server is only for migration and test purposes.

Let's see how it progresses......

IF (and that is a BIG IF at this time) and the migration goes well, will consider the next steps, for example, where to host the docker image, etc. But I don't want to get ahead of the tips of my skis since we have no idea how the migration will go.

I may also consider porting over the legacy user avatars.... not sure about this yet.
These 3 Users Gave Thanks to Neo For This Post:
 

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
dsimport(1)						    BSD General Commands Manual 					       dsimport(1)

NAME
dsimport SYNOPSIS
dsimport filepath nodepath O|M|A|I|N [options] dsimport --version dsimport --help DESCRIPTION
dsimport is a tool for importing records into an Open Directory source. USAGE
filepath is the path of the file to be imported. nodepath is the path of the Open Directory node where the records should be imported. A flag that specifies how to handle conflicting records: O overwrite of any existing records that have the same record name, UID or GID. All previous attribute values are deleted. M merge import data with existing records or create the record if it does not exist. I ignore the record if there is a conflicting name, UID or GID. A append the data to existing records, but do not create a record if it does not exist. N no duplicate checking should be done. Note this could cause failures and/or a slower import process. A list of options and their descriptions: --crypt is used to signify that all user passwords are crypt-based. Entries in the import file can also be prefixed with {CRYPT} on a per record basis if not all users are crypt-based. By default all passwords are assumed to be provided as listed in the import file. --force attribute value forces a specific value for the named attribute for all records during the import. The new value will overwrite any value specified in the import file. This option may be specified multiple times for forcing more than one attribute. --groupid value is the GID used for any records that do not specify a primary GID. --grouppreset value designate a preset record to be applied to imported group records. --loglevel value changes the amount of logging detail output to the log file. --outputfile value Outputs a plist to the specified file with a list of changed users or groups and rejected records due to name conflicts. Also includes a list of deleted records (overwrite mode), and lists of records that failed and succeeded during import. The format of this file is likely to change in a future release of Mac OS X. --password value is the admin's password for import operations. Used to authenticate to the directory node during import. A secure prompt will be used for interactive input if not supplied via parameter. Using the prompt method is the most secure method of providing password to dsimport. --recordformat string passes in the delimiters and attributes and record type to specify the order and names of attributes in the file to be imported. An example record format string: 0x0A 0x5C 0x3A 0x2C dsRecTypeStandard:Users 7 dsAttrTypeStandard:RecordName dsAttrTypeStandard:Password dsAttrTypeStandard:UniqueID dsAttrTypeStandard:PrimaryGroupID dsAttrTypeStandard:RealName dsAttrTypeStandard:NFSHomeDirectory dsAttrTypeStandard:UserShell A special value of IGNORE can be used for values that should be ignored in the import file on a record-by-record basis. --recordtype type Override the record type defined in the import file. For example, to import ComputerGroups as ComputerLists, use: --recordtype dsRecTypeStandard:ComputerLists The opposite works for importing ComputerLists as ComputerGroups, and so on. --remotehost hostname | ipaddress connects to a remote host at the network address specified. Commonly used to import to a remote Mac OS X Server. --remoteusername value specifies user name to use for the remote connection. --remotepassword value specifies password to use for the remote connection. A secure prompt will be used to ask for the password if --remoteusername is specified and --remotepassword is not. Using the prompt method is the most secure method of providing password to dsimport. --startid value indicates the ID number to start with when the import tool generates user or group IDs for any import file that lacks an ID as part of the import data. --template StandardUser | StandardGroup is used for delimited import of files that lack field descriptions. StandardUser contains the following fields in the order: 1. RecordName 2. Password 3. UniqueID 4. PrimaryGroupID 5. DistinguishedName 6. NFSHomeDirectory 7. UserShell StandardGroup contains the following fields in the order: 1. RecordName 2. Password 3. PrimaryGroupID 4. GroupMembership --username value is the admin username to use when importing records. If this is not specified the current user is the default name. Also, if used in conjunction with --remotehost then this admin user will be used for the Open Directory node whereas the username provided in --remoteusername will be used for the remote connection. If this option is left off but --remoteusername is provided, then the remote username will be used for both the connection and for importing records. --userpreset value designate a preset record to be applied to imported user records. EXAMPLES
To import a standard dsexport file into the Local database: dsimport myimportFile /Local/Default I --username administrator --password adminpassword FILES
/usr/bin/dsimport ~/Library/Logs/ImportExport SEE ALSO
DirectoryService(8) dsexport(1) Darwin May 31, 2019 Darwin
All times are GMT -4. The time now is 08:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy