Raspberry Gateway : Add variable in conf to modify service name

[3daerovision]

Hi,
Would it be possible to add a parameter in the configuration to change the name of the generated binairy / service ?
Thanks :)

[mfalkvidd]

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.

[3daerovision]

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.

[mfalkvidd]

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.

[mfalkvidd]

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.

[3daerovision]

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.
So, maybe just add the name for service in config file is enough ?

[mfalkvidd]

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.

[mfalkvidd]

Here is what I'm thinking so far:

• Add the service name to each log message. That would make it possible to read the log file even if multiple instances use the same log file/pipe.
• At startup, log the full file name and path for eeprom file and config file
• Create a file lock on the eeprom file, and fail startup if the gateway cannot get the lock.

I'm not sure these are the best options, or if they will be sufficient to keep most people out of trouble.

[mfalkvidd]

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.

[mfalkvidd]

@3daerovision when you have time, could you please test #1421 ?

[mfalkvidd]

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.

[mfalkvidd]

@3daerovision have you had any opportunity to test #1421 ?