-
-
Notifications
You must be signed in to change notification settings - Fork 894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Gateway : Add variable in conf to modify service name #1407
Comments
Thanks for suggesting this. Could you share the main reason for wanting to rename the binary and service? Understanding the main reason can be good so we don't miss some small but important aspect related to the rename. |
I run 2 instances of the service on my Raspberry, for 2 transport mode. Changing the name in the config would make this easier. But it could be usefull if someone wan't to test different setting without replacing his working instance of the service. |
I have started work on this. Service naming works, but to make it possible to run more than 1 instance we need to separate the configuration file, eeprom file, log file, log pipe and maybe more. |
Service rename works, but we also need to handle config file, log file, log pipe, eeprom file and maybe something more. This feature was requested in mysensors#1407
I'm worried that people will be confused when they compile and run two gateways with different service names, but same config file, log file, etc. I have not found a good way to handle this. Suggestions are welcome. |
I understand. I was not thinking of having multiple gateways on one config file, but more like multiple directories, with as many config and log files. For my tests, I have 2 separate MYS directories, have build both with different config, and then I had to rename the executable file and in services. I can run both without problem. |
For brand new installations, we could add the name of the service as a setting in the config file, and let the gateway check the name at startup and refuse to start if the name doesn't match. But then we'd need a safe way to handle modification of the config file when people upgrade. |
Here is what I'm thinking so far:
I'm not sure these are the best options, or if they will be sufficient to keep most people out of trouble. |
New updates in https://github.com/mfalkvidd/MySensors/tree/rpi-servicename Unfortunately, I am not skilled enough to figure out how to lock the eeprom file. |
@3daerovision when you have time, could you please test #1421 ? |
I did some work trying to lock the eeprom file last weekend, thanks to hints from Yveaux. Judging by the progress so far, I'll need multiple more weekends to figure out how to do it. |
@3daerovision have you had any opportunity to test #1421 ? |
Hi mfalkvidd, Is your work in the master or the development branch? |
The work is on the development branch. There are now two ways to use a radio and rs485.
|
If i want to make two instance of the gateway on the Raspberry i get te following: This is the configure command: Its not very clear how to make the two instance of the gateway. For cloning i used: |
#1421 has not been merged yet, so the service name feature is not available in the MySensors development branch. |
Hi,
Would it be possible to add a parameter in the configuration to change the name of the generated binairy / service ?
Thanks :)
The text was updated successfully, but these errors were encountered: