Re: dvswitch.ini multiple instances
MMDVM_Birdge will find MMDVM.ini in 2 ways.
If you just run ./MMDVM_Bridge it will look for the MMDVM.ini in the /etc directory if you have MMDVM_Bridge and MMDVM.ini in the same directory, run ./MMDVM_Bridge MMDVM.ini
It comes down to, Linux needs to know where the program is and MMDVM_Bridge needs to know where MMDVM.ini is.
MMDVM_Bridge will look for DVSwitch in the same directory as MB.
This is the best I can do typing on a phone.
Sent via smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Russell, KV4S <russelljthomas@...>
Sent: Friday, February 8, 2019 10:36:49 PM
Subject: Re: [DVSwitch] dvswitch.ini multiple instances
I understand what you are saying. the directories make the difference not the file names. I've tried it with just distinct folder names then renaming the files in the folders, I've tried it both ways.
What OS are you using?
What I'm experiencing goes against how I think it's supposed to work and even what you are saying.
I've mainly been experimenting with a personl bridge on a PI where i have different talk groups linked to different private nodes and one DMR to YSF bridge.
I'm changing the ports in the dvswitch.inis like I should be no port duplication on what's being used.
I'm thinking something is conflicting. For example i downloaded an mmdvm ini from a server i worked on from someone else. I had it in the home directory.
i coped it to where the program is running modified it for what I needed but when the node logged into brandmeister it kept trying to talk on the TG that was listed in the home directories ini not where i was telling it mmdvm's ini? does that make sense? Also, i made my talk group static set it in brandmeister dashboard but it was making a dynamic tg to the other bridge in the cloud that had nothing to do with what was on the pi other that the ini i downloaded was in the /home directory.
when i deleted the home directories ini and restarted mmdvm that problem with the dashboard went away.
I'm making copies of everything, mmdvm, analog, and md380 each instance is in a unique folder, each file has a unique name except the dvswitch.ini.
same goes for all the services. I have the md380 on different ports as well.
I'm not saying it's perfect but I feel like I've done a pretty good job of making sure evething is setup like it should be. this conflict with audio and the bm dashboad is making me thing maybe there is a bug going on somewhere? maybe it's something weird with the PI OS?
On Fri, Feb 8, 2019 at 9:20 PM Steve KC1AWV <smiller@...> wrote: