Hi Giuseppe, > > [...] > > The question is: could you confirm that you cannot > > add/remove/start/stop > > IAX devices without stopping the iaxmodem.service? In other words, no > > (device) events would be possibile once iaxmodem is started? > > No. You can add/remove devices with a seperate call of iaxmodem > > <configfile> while iaxmodem.service is running. You can even (re)start > > running devices. There is no lock or similar for a device once iaxmodem > > is started. > > > > Could you please verify if any of the proposed configuration works also > when adding/removing a new IAX device when iaxmodem is already up and > running? Same. I think the behavior is not a systemd issue but an issue of iaxmodem. Once iaxmodem is started, it reads all available config files and assigns any existing symlinks to a new device of /dev/pts/<n>. It doesn't check if it's already running and just overwrites existing symlinks. It doesn't terminate itself either, so any previously started process of iaxmodem remains still active. So, when I type /usr/bin/iaxmodem two times, the result with two available configfiles under /etc/iaxmodem is four iaxmodem processes running at the same time.
As far as I understand the code of iaxmodem.c this is the intended behavior (which, for me, is wrong). Maybe I should file a bug report against iaxmodem first before we work on faxgetty's systemd unit - what do you think? Thanks, Tino
