Re: Nov 11 2023 New version of the one-step ScarletDME installer

[Nivethan T]

Due to the interest in multi-tenanting, anyone know if it's as simple as changing the binaries to scarletdme and setting up a /usr/sdme folder?

I'd be happy to take a stab at investigating but this may be one of those things someone knows off the top of their head.

On Saturday, November 11, 2023 at 12:17:21 PM UTC-5 Donald Montaine wrote:

Is available on github at https://github.com/dmontaine/ScarletDME64_Installer

I corrected some typos.

Changed the install to make it possible for the root user to re-compile the

c source code after installation.

Added "nosudo" versions of the scripts for those who don't have sudo installed.

Added checks so that the installers will not run if a version of qm already

exists in /usr/qmsys/bin.

Added checks so the delete scripts will not attempt to run if qm is not installed

in /usr/qmsys/bin.

Note: this installer is a bit different from the 'official' repository. The makefile has been modified and some additional files are added to an installed system to allow re-compilation of the c source after installation. Other than those structural changes, no changes have been maded to the c code in gplsrc or the Basic code in GPL.BP from that provided in the dev branch of the geneb/ScarletDME repository on github.  I created this installed to provide an easier way to test the open source version of qm.

The pcloud link for this updated installer is: https://u.pcloud.link/publink/show?code=XZJmkoVZpjftBlgpobJEJy9UEimA74CvcwY7

[Nextjob]

This conversation touches on the subject:

https://groups.google.com/g/openqm/c/MSOi1aW7-oQ/m/Err5tmsDzmwJ

And there is this note in qmdefs.h (ln 99):

#define QM_SHM_KEY 0x716d0101
#define QM_SEM_KEY 0x716d0102
/* To allow the GPL version and the chargeable version of QM to
 * coexist, GPL developers should use keys with the third byte
 * non-zero for any future values.                              
 */

Good Luck!

[Donald Montaine]

I had posted  part of this previously in the multi-value group.  At least these changes would need to be made

shut down the existing commercial qm instance with qm -stop

Change everything in the script that reference /usr/qmsys to a different location

*Change the scarletdme.conf that gets written to /etc to reference QMSYS to a different directory

*You would also have to change settings in the scarlet*.server and scarlet*.socket files in the

/usr/lib/systemd/system directory.

*(easiest to do after install, so that is why turn off existing qm) first

Set up two different telnet ports if using telnet for direct access

Have two different home directories for each user, one for Commercial QM and one for ScarletDME

For users using SSH, probably write a bash script that allows the user to choose which system to log into.

These are the changes I can think of quickly.  However there may be more configuration changes

that would have to be made

As I mentioned before, the current version of commercial qm is designed to allow multi-tenanting. The version of qm that scarletdme was based on did not have that capability.  In fact the original OpenQM GPL version was based on inetd, not systemctl.  The systemctl support has been added by the current 

developers.

The bash installer script was not designed to co-exist with an existing qm installation.  Actually that can be 

said for the OpenQM 2.6.6 commercial installer as well.