03-11-2020
Hi Neo,
I assume nobody ever will do a migration/upgrade of a software like the vBulletin used at unix.com for a fixed price. That's beause I assume vBulletin here is absolutely heavily customized, to get really advanced and unique features, so the chances that the upgrade scripts will fail are very high. But I'm not sure for that.
That's the cost of customizations:
- Customizations may interfere with upgrade procedures
- Customized functionality may not work after an upgrade, and need to be fixed and maybe integrated in other ways.
So maybe to just customize the vb-importer of discourse is the best way to go. But hey - if someone says he/she can upgrade the current installation for a relatively small price, why not give a try....
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
LEARN ABOUT V7
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)