Hi Giuseppe, > The problem is if we may just wait for iaxmodem or if we need to wait for > the device. I agree.
> The dev-%i.device has events when udev sends them, but since that path is > not a real device, no udev events are sent. This probably means that using > dev-%i.device on any systemd unit is useless. I don't think they're useless. The intended behavior (from my understanding) of BindsTo=dev-%i.device is, to make sure faxgetty binds to that device and start it once the device becomes available or terminate it immediately when the underlying real device (say: /dev/ttyS0) is not available anymore. Therefore, the BindsTo-dependency makes sense to me. And this is why I wanted to keep them and add iaxmodem.service in this line with an OR statement, which seems not to be supported by systemd. > So, I am wondering if the minimal working unit is just > > [Unit] > Description=HylaFAX faxgetty %I > BindsTo=iaxmodem.service > After=iaxmodem.service This works. > 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. Thanks, Tino
