[arch-general] Anyone running hylafx with systemd - modem init/respawn OK?
Guys, Before I cause myself headaches -- is there anyone that has updated to systemd running a hylafax server with traditional serial modems? I see that systemd has the faxq.service and hafaxd.service: usr/lib/systemd/system/faxq.service usr/lib/systemd/system/hfaxd.service But what about the init and respawn of faxgetty that was usually done through inittab? mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS1 This may not even be an issue on Arch, but there have been issues with systemd on suse, etc. not handling the modem initialization after update to systemd. So before I end up with an issue, I thought I would ask if anyone else has made the jump to systemd with hylafax. -- David C. Rankin, J.D.,P.E.
On Sun, Jun 3, 2012 at 5:11 AM, David C. Rankin
But what about the init and respawn of faxgetty that was usually done through inittab?
mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS1
It would be done with a .service unit as well, similar to the existing getty@.service and serial-getty@.service. I'm not sure why one wasn't included with hylafax, but it should probably look like this: [Unit] Description=Faxgetty on %I BindTo=dev-%i.service After=dev-%i.service [Service] ExecStart=-/usr/lib/fax/faxgetty /dev/%I Restart=always ; I'm not sure if the following are strictly necessary, but they ; are used by existing getty units. UtmpIdentifier=%I TTYPath=/dev/%I TTYReset=yes TTYVHangup=yes (Note: Untested. I don't actually have the hardware.) -- Mantas Mikulėnas
participants (2)
-
David C. Rankin
-
Mantas Mikulėnas